Hugo Nijhuis
cdfacbac18
- Move legacy content to legacy/ folder (old, old2, docs, learnings, scripts) - Create new .opencode/ structure with skills/, tools/, agents/ folders - Update Makefile to symlink to ~/.config/opencode/ instead of ~/.claude/ - Update Makefile to manage skills, tools, and agents (remove settings.json) - Simplify install/uninstall (no backup logic) - Add README.md documenting the new structure - Keep settings.json as historical reference
1.4 KiB
1.4 KiB
name, description, model, argument-hint, user-invocable
| name | description | model | argument-hint | user-invocable | |
|---|---|---|---|---|---|
| groom | Groom and improve issues. Without argument, reviews all open issues. With argument, grooms specific issue. Use when grooming backlog, improving issues, or when user says /groom. | sonnet |
|
true |
Groom Issues
@/.claude/skills/gitea/SKILL.md
@/.claude/skills/backlog-grooming/SKILL.md
@~/.claude/skills/issue-writing/SKILL.md
If issue number provided ($1):
- Fetch the issue details with
tea issues <number> --comments - Check dependencies with
tea issues deps list <number> - Evaluate against grooming checklist
- Suggest improvements for:
- Title clarity
- Description completeness
- Acceptance criteria quality
- Scope definition
- Missing or incorrect dependencies
- Ask user if they want to apply changes
- Update issue if approved
- Link/unlink dependencies if needed:
tea issues deps add/remove <issue> <dep>
If no argument (groom all):
- List open issues
- Review each against grooming checklist (including dependencies)
- Categorize:
- Ready: Well-defined, dependencies linked, can start work
- Blocked: Has unresolved dependencies
- Needs work: Missing info, unclear, or missing dependency links
- Stale: No longer relevant
- Present summary table with dependency status
- Offer to improve issues that need work (including linking dependencies)