Claude Skill MartBrowse skillsWhat is a Skill?
 
← Back to list

GitHub Triage (Read-Only)

Analyzes every open issue and PR in parallel and writes evidence-backed triage reports — without ever mutating GitHub.

Dev & CodingIntermediate★ 67,531⑂ 5,507AI score 7/10Last updated: Aug 9, 2026

What it does

  • Uses the gh CLI to fetch all open issues and PRs in the current repo, with 500-item pagination for large backlogs.
  • Classifies each item (question / bug / feature / other; PRs as bugfix / other).
  • Spawns one background subagent per item, analyzing them concurrently and writing reports to /tmp/{YYYYMMDD-HHmmss}/issue-123.md or pr-45.md.
  • Enforces an evidence rule: every factual claim needs a commit-SHA permalink; unsupported statements must be marked [UNVERIFIED] or "No evidence found" (branch-name links are rejected).
  • Produces a final SUMMARY.md with per-category counts and an "items requiring attention" list.
  • Zero-action policy: no comments, merges, closes, labels, reviews, no gh api -X POST/PUT/PATCH/DELETE, and no git checkout of PR branches.

Who it's for

  • Open-source maintainers drowning in an issue/PR backlog.
  • Developers who need a fast, code-grounded verdict on whether a bug is real, already fixed, or invalid.
  • Cautious teams that want AI analysis but absolutely no writes to their repository.

Examples

  1. Backlog sweep: In a repo with 120 open issues, say "triage issues" and get a per-issue report plus CONFIRMED_BUG / ALREADY_FIXED / NOT_A_BUG verdicts.
  2. Pre-release PR sanity check: "triage PRs" yields a merge-readiness table (CI, review, mergeable, correctness, risk) with a MERGE / REQUEST_CHANGES / NEEDS_REVIEW recommendation per PR.
  3. Find already-fixed reports: It uses git log/git blame to locate the fixing commit, e.g. "#88 was fixed in a1b2c3d", with a commit permalink so you can confidently close stale issues.

· · · Install guide · · ·

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the .opencode/skills/github-triage folder from the GitHub repo code-yeongyu/oh-my-openagent into my ~/.claude/skills/code-yeongyu-github-triage/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/code-yeongyu/oh-my-openagent.git /tmp/oh-my-openagent && mkdir -p ~/.claude/skills && cp -r /tmp/oh-my-openagent/.opencode/skills/github-triage ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Prerequisites: install git, the GitHub CLI (gh), and jq, then run gh auth login.
  2. Clone the repository: git clone https://github.com/code-yeongyu/oh-my-openagent.git
  3. Copy the skill into place: mkdir -p ~/.claude/skills && cp -r oh-my-openagent/.opencode/skills/github-triage ~/.claude/skills/
  4. Verify that ~/.claude/skills/github-triage/SKILL.md exists.
  5. Restart Claude Code and cd into the repository you want to triage.
  6. Ask for it by trigger phrase: "triage issues", "triage PRs", or "github triage".
  7. Read the streamed output plus the markdown reports in /tmp/{timestamp}/.
  8. Note: the skill assumes opencode's background task tools (task_create, background_output). On stock Claude Code, parallel work maps to subagent calls instead — try it on a small repo first, since one subagent per open item can get expensive.
View source on GitHub ↗License: NOASSERTION