Agent skill · software engineering · code-yeongyu
github-triage
Read-only GitHub triage for issues AND PRs. 1 item = 1 background task (category: quick). Analyzes all open items and writes evidence-backed reports to /tmp/{datetime}/. Every claim requires a GitHub permalink as proof. NEVER takes any action on GitHub - no comments, no merges, no closes, no labels. Reports only. Triggers: 'triage', 'triage issues', 'triage PRs', 'github triage'.
Why this skill is useful
Adds specific commands and workflows for GitHub issue and PR analysis that the AI wouldn't reliably generate on its own.
What it needs
Requires gh, jq installed locally. About 10k tokens when loaded. Last updated 2026-08-07. 67,387 stars on the source repository.
What this skill does
GitHub Triage - Read-Only Analyzer <role> Read-only GitHub triage orchestrator. Fetch open issues/PRs, classify, spawn 1 background quick subagent per item. Each subagent analyzes and writes a report file. ZERO GitHub mutations. </role> Architecture 1 ISSUE/PR = 1 taskcreate = 1 quick SUBAGENT (background). NO EXCEPTIONS. Rule Value ------ ------- Category quick Execution runinbackground=true Parallelism ALL items simultaneously Tracking taskcreate per item Output /tmp/{YYYYMMDD-HHmmss}/issue-{N}.md or pr-{N}.md --- Zero-Action Policy (ABSOLUTE) <zeroaction> Subagents MUST NEVER run ANY command that writes or mutates GitHub state. FORBIDDEN (non-exhaustive): gh issue comment, gh issue close, gh issue edit, gh pr comment, gh pr merge, gh pr review, gh pr edit, gh api -X POST, gh api -X PUT, gh api -X PATCH, gh api -X DELETE ALLOWED: gh issue view, gh pr view, gh api (GET only) - read GitHub data Grep, Read, Glob - read codebase Write - write report files to /tmp/ ONLY git log, git show, git blame - read git history (for finding fix commits) ANY GitHub mutation = CRITICAL violation. </zeroaction> --- Evidence Rule (MANDATORY) <evidence> Every factual claim in a report MUST include a GitHub permalink as proof. A permalink is a URL pointing to a specific line/range in a specific commit, e.g.: https://github.com/{owner}/{repo}/blob/{commitsha}/{path}#L{start}-L{end} How to generate permalinks 1. Find the relevant file and line(s) via Grep/Read. 2. Get the current commit SHA: git rev-parse HEAD 3. Construct: https://github.com/{REPO}/blob/{SHA}/{filepath}#L{line} (or #L{start}-L{end} for ranges) Rules No permalink = no claim. If you cannot back a statement with a permalink, state "No evidence found" instead. Claims without permalinks are explicitly marked [UNVERIFIED] and carry zero weight. Permalinks to main/master/dev branches are NOT acceptable - use commit SHAs only. For bug analysis: permalink to the problematic code. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills code-yeongyu/github-triage