triage

GitHub issue triage automation uses a role-based state machine to recommend and apply category and state label transitions. It guides issues through canonical roles like needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix.

Yes, preparing GitHub issues for an AFK agent involves producing agent briefs using a durable contract format. This ensures the AFK agent can work without relying on stale file paths or line numbers.

Recording enhancement wontfix decisions requires writing or linking to .out-of-scope concept records. This builds a rejection knowledge base that enables deduplication and preserves institutional memory.

Issue triage gathers context by reading issue details, existing notes, relevant repo docs, and prior triage history. It uses this context to recommend the next role transition with supporting codebase evidence.

Yes, the triage workflow enforces durable agent-brief formatting requirements and disclaimer rules for AI-generated triage comments. It also mandates structured acceptance-criteria-driven outputs for ready states.

A structured state machine for GitHub label management is needed when triage coordination must be consistent, auditable, and faster. It guides maintainers through exact required outputs during workflow transitions.