Files
architecture/commands/groom.md
Hugo Nijhuis 68675a7e12 Migrate from Forgejo to Gitea
- Replace fj CLI with tea CLI across all commands
- Create new gitea skill, remove forgejo skill
- Update all agents to use gitea skill
- Update commands to use skill-based approach (reference skills instead of embedding CLI commands)
- Update all documentation (README, ARCHITECTURE, VISION, writing guides)
- Swap git remotes: origin now points to git.flowmade.one (Gitea)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-30 23:52:36 +01:00

869 B

description, argument-hint
description argument-hint
Groom and improve issues. Without argument, reviews all open issues. With argument, grooms specific issue.
issue-number

Groom Issues

Use the gitea, backlog-grooming, and issue-writing skills.

If issue number provided ($1):

  1. Fetch the issue details
  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

If no argument (groom all):

  1. List open issues
  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