Files
architecture/legacy/old/skills/groom/SKILL.md
Hugo Nijhuis cdfacbac18 Migrate from Claude Code to OpenCode structure
- 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
2026-05-02 13:41:59 +02:00

44 lines
1.4 KiB
Markdown

---
name: groom
description: >
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.
model: sonnet
argument-hint: [issue-number]
user-invocable: 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):
1. **Fetch the issue** details with `tea issues <number> --comments`
2. **Check dependencies** with `tea issues deps list <number>`
3. **Evaluate** against grooming checklist
4. **Suggest improvements** for:
- Title clarity
- Description completeness
- Acceptance criteria quality
- Scope definition
- Missing or incorrect dependencies
5. **Ask user** if they want to apply changes
6. **Update issue** if approved
7. **Link/unlink dependencies** if needed: `tea issues deps add/remove <issue> <dep>`
## If no argument (groom all):
1. **List open issues**
2. **Review each** against grooming checklist (including dependencies)
3. **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
4. **Present summary** table with dependency status
5. **Offer to improve** issues that need work (including linking dependencies)