Issue Triage

Triage messy GitHub issues by processing the issue text, prior comments, and repository context to generate structured triage notes, state recommendations, and an agent brief for actionable next steps.

Managing open-source issue workflows involves guiding incomplete bug reports through a structured state machine with roles like bug or enhancement, attempting codebase reproduction, and outputting labels with next steps.

Issue triage avoids redundant clarification questions by reading prior triage notes and comments, identifying missing details, and only requesting the specific information needed to advance the issue state.

You can use a state machine to categorize and route GitHub issues by enforcing role and state transitions such as needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix.

Reproduce bugs from GitHub issues by providing the issue text and relevant repository context, allowing the triage process to attempt failure confirmation in the codebase before recommending a state.

To generate an agent brief during GitHub issue triage, you need to provide the incoming issue text, prior comments or notes, and any relevant repository context to ensure clear implementation next steps.