GitHub Triage grooms a repository’s backlog when you run it. It can merge passing bot PRs and maintainer-approved PRs one at a time, spawn review subagents for PRs nobody has reviewed, close issues that are already resolved with a comment citing the resolving PR or commit, link issues to the open PRs that fix them, and rate everything still outstanding.
Every write to GitHub is shown for approval first. Priority and change-size estimates stay on your machine and are never posted.
What You Get
- A proposed list of issues to close, each with the merged PR or commit that resolves it
- Proposed cross-links between issues and the open PRs that fix them
- Priority (critical to low) and a size bucket from XS to XXL for every outstanding issue, with the basis of the estimate
- Markdown reviews of never-reviewed PRs saved as local files
- A saved triage report when more than 32 issues remain
Common Use Cases
- Clearing a backlog where fixes landed without closing their issues
- Merging a pile of green Dependabot or Renovate PRs in order
- Getting a first review of PRs that sit unreviewed
- Planning a sprint from sized and prioritized open issues
What Makes It Unique
It is built around safe writes. Nothing is closed, commented or merged until you approve the full set. Merges happen one at a time with the PR state re-checked before each, and never with force or auto-merge. Evidence is required for every close, fetched issue text is treated as data and not as instructions, and untrusted text never goes through shell interpolation. Priority and size are never posted to GitHub.
Under The Hood
The skill is prose with a reference file for PR review, and it must be invoked by you. The agent runs gh and git commands in the shell against the repository, reading issues and PRs through the GitHub API with your credentials. After you approve, it can merge PRs, close issues, post comments and edit PR bodies on GitHub. It also reads code to check whether an issue is resolved, dispatches review subagents in parallel, and writes review and report markdown files in the working directory.