github-triage

Triages open GitHub issues and pull requests with parallel read-only executor agents.

1|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/UtsavBalar1231/oh-my-claudeagent --skill github-triage-utsavbalar1231
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-triage
Source: https://github.com/UtsavBalar1231/oh-my-claudeagent/tree/main/skills/github-triage
Command: npx skills add https://github.com/UtsavBalar1231/oh-my-claudeagent --skill github-triage-utsavbalar1231

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually reviewing every open issue and pull request in a busy GitHub repository is slow and inconsistent. This Skill automates read-only triage by classifying each item and dispatching one background executor agent per item to produce evidence-backed reports. ## Core Features & Use Cases - Parallel per-item analysis: Spawns one background executor agent per issue or PR, batched at up to 5 concurrent agents, with run-size bounding and a SKIPPED.md overflow log. - Classification and verdicts: Classifies items as question, bug, feature, or other, and assesses PR merge safety against six explicit conditions including CI status, review decision, and conflicts. - Mandatory evidence citations: Every factual code claim must cite a GitHub permalink containing a commit SHA, otherwise it is marked UNVERIFIED. - Use Case: A maintainer returning to a repository with 80 open issues and 20 open PRs runs the triage to get per-item reports and a SUMMARY.md highlighting confirmed bugs, merge-safe PRs, and items needing human decisions. ## Quick Start Ask the agent to triage the open issues and pull requests in the current GitHub repository and summarize which items need attention.

Frequently Asked Questions about github-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage open GitHub issues automatically?

Invoke the skill against a repository and it fetches open issue metadata with gh issue list, classifies each item as question, bug, feature, or other, then spawns one background executor agent per item to write an evidence-backed report.

How to check if a GitHub PR is safe to merge?

The PR analysis evaluates six merge conditions: CI passing, approved review decision, verified fix correctness, no risky side effects, not a draft, and no merge conflicts. Each condition is reported in a checklist inside the per-PR report.

Can this skill close issues or merge pull requests?

No. The skill enforces a zero-action policy that forbids all GitHub mutations including gh pr merge, gh issue close, edits, comments, and non-GET API calls. It only reads data and writes local reports for human maintainers to act on.

What happens when a repository has hundreds of open issues?

The orchestrator picks a run-size bound, sorts items by most recently updated, and processes only that many. Skipped items are logged to SKIPPED.md and the overflow count is stated in SUMMARY.md so nothing is silently dropped.

Why are commit SHA permalinks required in triage reports?

Commit-SHA permalinks pin every code claim to an immutable revision, so evidence stays valid as branches change. Claims without such a citation must be marked UNVERIFIED, preventing unsupported statements about bugs or features.