triage-issue

Automate GitHub issue triage by using an agent-driven workflow that evaluates, classifies, and routes issues. It processes specific issue numbers or batches all open issues labeled state:triage-needed to generate actionable routing outputs.

Agent-first gate validation is an automated compliance check applied during issue triage. It assesses community-filed GitHub issues to ensure they meet required standards before attempting diagnosis and classifying them for the spike-build pipeline.

Yes, you can batch process triage for all open GitHub issues. The workflow specifically targets and evaluates all issues labeled state:triage-needed, applying structured diagnostics to guide routing into spike or build-from-issue workflows.

Yes, you need the GitHub CLI installed to classify and route repository issues. The workflow requires the gh CLI for repository inspection to fetch issue details and post triage markers for human-in-the-loop collaboration.

The best way to route diagnosed GitHub issues is through structured classification that guides them into spike or build-from-issue workflows. The triage process evaluates issues and generates actionable outputs to direct them appropriately.

Issues may not route correctly if they lack the state:triage-needed label or fail agent-first gate validation. The triage workflow requires proper permissions and the gh CLI to inspect repositories, diagnose issues, and post triage markers successfully.