Hugo Nijhuis
9c975c64ea
Skills require YAML frontmatter with name and description fields for Claude Code to automatically discover and load them. Added frontmatter to all five skill files: - gitea: CLI for issues, PRs, and repository management - code-review: Guidelines for reviewing code changes - issue-writing: How to write clear, actionable issues - backlog-grooming: Review and improve existing issues - roadmap-planning: Plan features and create issues Closes #12 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2.1 KiB
2.1 KiB
name, description
| name | description |
|---|---|
| issue-writing | How to write clear, actionable issues with proper structure and acceptance criteria |
Issue Writing
How to write clear, actionable issues.
Issue Structure
Title
- Start with action verb: "Add", "Fix", "Update", "Remove", "Refactor"
- Be specific: "Add user authentication" not "Auth stuff"
- Keep under 60 characters when possible
Description
## Summary
One paragraph explaining what and why.
## Acceptance Criteria
- [ ] Specific, testable requirement
- [ ] Another requirement
- [ ] User can verify this works
## Context
Additional background, links, or references.
## Technical Notes (optional)
Implementation hints or constraints.
Writing Acceptance Criteria
Good criteria are:
- Specific: "User sees error message" not "Handle errors"
- Testable: Can verify pass/fail
- User-focused: What the user experiences
- Independent: Each stands alone
Examples:
- [ ] Login form validates email format before submission
- [ ] Invalid credentials show "Invalid email or password" message
- [ ] Successful login redirects to dashboard
- [ ] Session persists across browser refresh
Issue Types
Bug Report
## Summary
Description of the bug.
## Steps to Reproduce
1. Go to...
2. Click...
3. Observe...
## Expected Behavior
What should happen.
## Actual Behavior
What happens instead.
## Environment
- Browser/OS/Version
Feature Request
## Summary
What feature and why it's valuable.
## Acceptance Criteria
- [ ] ...
## User Story (optional)
As a [role], I want [capability] so that [benefit].
Technical Task
## Summary
What technical work needs to be done.
## Scope
- Include: ...
- Exclude: ...
## Acceptance Criteria
- [ ] ...
Labels
Use labels to categorize:
bug,feature,enhancement,refactorpriority/high,priority/low- Component labels specific to project
Dependencies
Reference related issues:
- "Depends on #N" - Must complete first
- "Blocks #N" - This blocks another
- "Related to #N" - Informational link