triage-issue

You can triage a single GitHub issue by providing its issue number, or batch process all open issues carrying the state:triage-needed label. This automates assessment, classification, and routing to reduce manual triage overhead.

Yes, batch triage processes all open GitHub issues labeled state:triage-needed automatically. It enforces agent-first gate validation, uses relevant skills for diagnosis, and classifies issues for routing into the spike-build pipeline.

Agent-first gate compliance validates GitHub issues automatically during the triage process. It enforces required gate checks, uses relevant skills for diagnosis, and ensures issues meet criteria before routing them into the spike-build pipeline.

The best way to route classified GitHub issues is to automate their assessment and classification during triage. By enforcing agent-first gate compliance, issues are properly categorized and routed directly into the spike-build pipeline.

Yes, automated issue triage works by assessing and classifying issues based on existing GitHub labels and issue content. It uses this data to enforce agent-first gate validation and route items into the appropriate pipeline.