Triages a repository's open GitHub issues and pull requests via the gh CLI. Optionally reviews and merges ready PRs — incrementally merging passing automated/bot PRs and maintainer-approved ones, and spawning review subagents for never-reviewed ones — then closes already-resolved issues with comments citing the resolving PR or commit, cross-links issues with their pending fix PRs, and assigns local-only priority and change-size estimates for everything outstanding.
SkillScore80Maintained
On-demandOn-demand: invoked explicitly — never occupies your agent's context until called.
◆Coding pack
Last verified 8/7/2026
What it changes
Passed 18 of 22 test cases with the skill, and 14 of 22 without it.
Without skill64%
With skill80%
Checks it passed that the model alone missed
The response classifies a 45-line diff into the size/M bucket.
The response assigns the status unsized — needs investigation to vague issues.
The response re-queries PR state with gh pr view immediately before executing each merge.
and 2 more in the full report
5 fixed15 passed either way4 still failing1 broke
Pass-rate lift
+16 pp
Tokens
+329%
Agent turns
0%
Response time
-52%
Model gemini-3.6-flashMeasured 8/7/2026v120 of 25 cases passed with skill · 22 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
We approved merging 3 bot PRs (#10, #11, #12). PR #10 was merged successfully. Before executing gh pr merge for #11, what action must be taken?
What was checked, without and with the skill
Checked
Without skill
With skill
The response re-queries PR state with gh pr view immediately before executing each merge.
Missed
Passed
case-21 · gemini-3.6-flash · 8/7/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md403 lines3 files
GitHub Triage
Triage a repository's open GitHub issues and pull requests. Optionally clear ready
PRs first (merge passing bot PRs and maintainer-approved PRs, review never-reviewed
ones), then close issues that are already resolved (with a comment citing the PR or
commit that resolved them), make sure issues and the pending PRs that fix them
reference each other, and assign a local-only priority and change-size estimate
to every issue that is still outstanding.
When to Use
When the user runs /github-triage to groom or review a repository's open issues
and pull requests.
When an issue backlog has drifted: resolved work left open, fixes landed without
closing their issues, or PRs in flight that never linked their issue.
When ready PRs have piled up (passing dependency bumps, approved-and-green PRs) or
PRs are sitting unreviewed.
When NOT to Use
Do not invoke automatically. This skill performs irreversible GitHub writes
(merging PRs, closing issues, posting comments) and runs only on explicit invocation.
Do not use to apply priority/effort labels on GitHub. Priority and size are
presented locally only and are never posted (see Safety Rules).
Do not use as a substitute for a human's final merge decision — every merge is
proposed for explicit approval, never performed autonomously.
Core Principles
Writes are gated. Compute the full triage first, present every proposed
write — merges included — for review, and execute nothing until the user approves.
Evidence before closing. Never close an issue without a concrete, cited
reason (a merged PR or a commit on the default branch). When evidence is weak
or ambiguous, leave the issue outstanding and flag it for review.
Priority and size stay local. They are an internal planning aid for the
user, never written to GitHub.