github-triage

name	github-triage
description	Triage GitHub issues through a label-based state machine with interactive grilling sessions. Use when user wants to triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.

GitHub Issue Triage

Triage issues in the current repo using a label-based state machine.

AI disclaimer

Any GitHub comment created during triage must start with:

> *This was generated by AI during triage.*

Labels

Every issue should have exactly one category label and one state label.

Category labels:

• bug
• enhancement

State labels:

• needs-triage
• needs-info
• ready-for-agent
• ready-for-human
• wontfix

If labels conflict, stop and resolve the conflict first.

Core workflow

1. Read the full issue and all comments.
2. Explore the codebase for context.
3. Read .out-of-scope/*.md for matches.
4. Recommend category and next state with reasons.
5. For bugs, try to reproduce before grilling.
6. When moving to ready-for-agent, write a durable agent brief.
7. When rejecting an enhancement as wontfix, record it in .out-of-scope/.

See AGENT-BRIEF.md and OUT-OF-SCOPE.md.