Hugo Nijhuis
bbd7870483
Set explicit model preferences to optimize for speed vs capability: - haiku: 11 commands, 2 agents (issue-worker, pr-fixer), 10 skills Fast execution for straightforward tasks - sonnet: 4 commands (groom, improve, plan-issues, review-pr), 1 agent (code-reviewer) Better judgment for analysis and review tasks - opus: 2 commands (arch-refine-issue, arch-review-repo), 1 agent (software-architect) Deep reasoning for architectural analysis Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1.3 KiB
1.3 KiB
description, model, argument-hint
| description | model | argument-hint | |
|---|---|---|---|
| Groom and improve issues. Without argument, reviews all open issues. With argument, grooms specific issue. | sonnet |
|
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)