issue-triage

You can automatically classify and label GitHub issues by providing an issue number or URL to trigger end-to-end triage. The system determines if the issue is a bug, enhancement, question, docs, or dependency request, applies the correct label, and routes it to the matching workflow.

Issue triage routing works by applying type-specific workflows after classification. Bug reports trigger reproduction and fix-PR creation workflows, while enhancement requests trigger a feature specification check to ensure there is only one way to do one thing.

To start triaging a GitHub issue, you need to provide the issue number, paste a GitHub URL, or use trigger keywords like triage, look at, handle, or process. The system then reads the issue and handles classification, labeling, and routing automatically.

Yes, you can trigger GitHub issue classification using natural language commands. The system recognizes specific triage keywords such as triage, look at, handle, or process in your input to initiate the end-to-end labeling and routing workflow.

Yes, the automated issue labeling process requires confirmation before any public GitHub actions. The system enforces a one-issue-per-invocation discipline and uses a confirmation gate to ensure safe and deliberate modifications.

The best way to handle GitHub issue routing for documentation and dependencies is through automated triage classification. The system identifies these specific issue types, applies the correct labels, and routes them to the appropriate specialized workflow.