Hugo Nijhuis
1c0b6b3712
Updated skills and commands to identify and formally link issue dependencies using tea CLI: Skills updated: - issue-writing: Document deps in description + link with tea CLI - backlog-grooming: Check for formal dependency links in checklist - roadmap-planning: Link dependencies after creating issues Commands updated: - create-issue: Ask about and link dependencies for new issues - plan-issues: Create in dependency order, link with tea issues deps add - groom: Check dependency status, suggest missing links 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1.3 KiB
1.3 KiB
description, argument-hint
| description | argument-hint | |
|---|---|---|
| Groom and improve issues. Without argument, reviews all open issues. With argument, grooms specific issue. |
|
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)