- Add groom, plan-issues, and roadmap commands - Add skills for backlog-grooming, forgejo, issue-writing, roadmap-planning - Add agents directory structure - Remove load-forgejo-token.sh and SessionStart hook (using fj auth instead) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
32 lines
933 B
Markdown
32 lines
933 B
Markdown
---
|
|
description: Groom and improve issues. Without argument, reviews all open issues. With argument, grooms specific issue.
|
|
argument-hint: [issue-number]
|
|
---
|
|
|
|
# Groom Issues
|
|
|
|
Use the backlog-grooming and issue-writing skills.
|
|
|
|
## If issue number provided ($1):
|
|
|
|
1. **Fetch the issue**: `fj issue view $1`
|
|
2. **Evaluate** against grooming checklist
|
|
3. **Suggest improvements** for:
|
|
- Title clarity
|
|
- Description completeness
|
|
- Acceptance criteria quality
|
|
- Scope definition
|
|
4. **Ask user** if they want to apply changes
|
|
5. **Update issue** if approved: `fj issue edit $1 --body "..."`
|
|
|
|
## If no argument (groom all):
|
|
|
|
1. **List open issues**: `fj issue search -s open`
|
|
2. **Review each** against grooming checklist
|
|
3. **Categorize**:
|
|
- Ready: Well-defined, can start work
|
|
- Needs work: Missing info or unclear
|
|
- Stale: No longer relevant
|
|
4. **Present summary** table
|
|
5. **Offer to improve** issues that need work
|