github-triage

To automatically triage GitHub issues and pull requests, you can use a skill that fetches repository metadata and classifies entries by type, such as bug or feature request. This process generates evidence-backed markdown reports without modifying repository state.

Automated GitHub issue triage generates evidence-backed reports by fetching metadata via the GitHub CLI and jq, then spawning background analysis tasks. Every classification claim in the report links directly to a relevant GitHub permalink for verification.

Yes, you need the GitHub CLI and jq installed to analyze open issues and pull requests. These dependencies are required to process repository data, fetch metadata, and generate the detailed markdown triage reports.

Yes, you can use automated triage for repositories with hundreds of open issues. The skill fetches all open issues and PRs, classifies them by type, and identifies which are confirmed bugs or require immediate attention, handling large volumes effectively.

No, read-only GitHub issue triage does not modify your repository state. It only fetches metadata to perform classification and analysis, ensuring your repository remains completely untouched while generating summary reports.

The best way to categorize bugs and feature requests in GitHub is through automated triage that fetches issue metadata and applies classification logic. This identifies confirmed bugs, feature requests, and questions, outputting a detailed markdown summary.