Issue and PR triage
Triages issues and external PRs on the tracker: gives each a category and a state, checks for existing code and past rejections, reproduces bugs and writes agent briefs for ready work. Use when a maintainer works through incoming issues and PRs.
triage- Author
- Matt Pocock
- Source
- mattpocock/skills/skills/engineering/triage @ abeeaf9
- License
- MIT · Copyright (c) 2026 Matt Pocock
About this skill
What it does
Triage runs a maintainer's issue tracker as a small state machine. Every issue gets one category, bug or enhancement, and one state: needs-triage, needs-info, ready-for-agent, ready-for-human or wontfix. External pull requests can go through the same states.
"Show me anything that needs my attention" returns three buckets, oldest first: unlabeled, needs-triage, and needs-info where the reporter has replied. For one issue or PR the agent reads everything, checks for an existing implementation and past rejections, recommends a category and state, and waits. Then it verifies the claim: reproduces the bug, or checks out the PR and runs its tests. A thin request gets grilled into shape. The outcome is an agent brief, triage notes with specific questions for the reporter, or a close. Every comment opens with a line saying AI wrote it during triage.
AGENT-BRIEF.md explains the brief an unattended agent works from: behaviour instead of file paths and line numbers, testable acceptance criteria, explicit out of scope, with examples for a bug, an enhancement and a PR. OUT-OF-SCOPE.md describes the .out-of-scope/ folder: one file per rejected concept with the reasoning and the issues that asked for it, matched by meaning, not keywords.
When to use it, and when not
Use it on a project with a steady flow of outside issues and PRs whose ready work goes to agents, not for your own work in progress.
It needs the tracker, a mapping from its role names to your real labels and, for PRs, who counts as external. The author's setup-matt-pocock-skills writes that config but is not in our catalog; you can tell the agent yourself.
How to run it
The install command below puts the whole folder in place. With disable-model-invocation: true it runs only when called:
- Claude Code: only the
/triagecommand — naming the skill in a message will not start it. - Codex:
$triage. - Cursor: type
/in the Agent chat and picktriage.
Example: /triage Show me what needs my attention, then let's look at the oldest bug.
Grilling calls Grilling a plan and Domain modeling; install them too.
How it differs from similar skills
Linear issues and projects also moves issues between states and applies labels, but only in Linear and without a fixed set of states, claim verification or agent briefs. PR review reads a diff for bugs before a merge; triage decides what happens to a PR next and briefs whoever finishes it. Log triage shares the word but reads logs. ready-for-agent is the state Conversation to spec and Spec to tickets give their output.
Install
Run one command — it saves SKILL.md and the files it uses into your agent's skills folder. Claude Code and Codex pick up a new skill without a restart; if it does not show up, restart the agent.
curl -fsSL --create-dirs -o ~/.claude/skills/triage/SKILL.md https://anymodel.org/en/skills/matt-pocock/triage/SKILL.md -o ~/.claude/skills/triage/AGENT-BRIEF.md https://anymodel.org/en/skills/matt-pocock/triage/AGENT-BRIEF.md -o ~/.claude/skills/triage/LICENSE https://anymodel.org/en/skills/matt-pocock/triage/LICENSE -o ~/.claude/skills/triage/OUT-OF-SCOPE.md https://anymodel.org/en/skills/matt-pocock/triage/OUT-OF-SCOPE.md -o ~/.claude/skills/triage/agents/openai.yaml https://anymodel.org/en/skills/matt-pocock/triage/agents/openai.yaml
curl -fsSL --create-dirs -o ~/.agents/skills/triage/SKILL.md https://anymodel.org/en/skills/matt-pocock/triage/SKILL.md -o ~/.agents/skills/triage/AGENT-BRIEF.md https://anymodel.org/en/skills/matt-pocock/triage/AGENT-BRIEF.md -o ~/.agents/skills/triage/LICENSE https://anymodel.org/en/skills/matt-pocock/triage/LICENSE -o ~/.agents/skills/triage/OUT-OF-SCOPE.md https://anymodel.org/en/skills/matt-pocock/triage/OUT-OF-SCOPE.md -o ~/.agents/skills/triage/agents/openai.yaml https://anymodel.org/en/skills/matt-pocock/triage/agents/openai.yaml
foreach ($f in 'SKILL.md','AGENT-BRIEF.md','LICENSE','OUT-OF-SCOPE.md','agents/openai.yaml') { $p = Join-Path "$HOME\.claude\skills\triage" $f; New-Item -ItemType Directory -Force (Split-Path $p) | Out-Null; Invoke-WebRequest "https://anymodel.org/en/skills/matt-pocock/triage/$f" -UseBasicParsing -OutFile $p }foreach ($f in 'SKILL.md','AGENT-BRIEF.md','LICENSE','OUT-OF-SCOPE.md','agents/openai.yaml') { $p = Join-Path "$HOME\.agents\skills\triage" $f; New-Item -ItemType Directory -Force (Split-Path $p) | Out-Null; Invoke-WebRequest "https://anymodel.org/en/skills/matt-pocock/triage/$f" -UseBasicParsing -OutFile $p }Any other agent: save the file into its skills folder, or give it the link to the file: https://anymodel.org/en/skills/matt-pocock/triage/SKILL.md
SKILL.md
Triage
Move issues on the project issue tracker through a small state machine of triage roles.
If this repo treats external pull requests as a request surface (see the issue-tracker config), triage covers them too: a PR is an issue with attached code, using the same roles, same states, and same machine, with a few deltas marked "for a PR" below. Resolve a bare #42 to an issue or PR per the tracker config.
Every comment or issue posted to the issue tracker during triage must start with this disclaimer:
> *This was generated by AI during triage.*
Reference docs
- AGENT-BRIEF.md: how to write durable agent briefs
- OUT-OF-SCOPE.md: how the
.out-of-scope/knowledge base works
Roles
Two category roles:
bug: something is brokenenhancement: new feature or improvement
Five state roles:
needs-triage: maintainer needs to evaluateneeds-info: waiting on reporter for more informationready-for-agent: fully specified, ready for an AFK agentready-for-human: needs human implementationwontfix: will not be actioned
For a PR, the same states read against the attached code: ready-for-agent means a brief is attached and an agent should take the next step on the diff; ready-for-human means it's ready for a human to merge.
Every triaged issue should carry exactly one category role and one state role. If state roles conflict, flag it and ask the maintainer before doing anything else.
These are canonical role names. The actual label strings used in the issue tracker may differ. The mapping should have been provided to you. If not, tell the user to run /setup-matt-pocock-skills.
State transitions: an unlabeled issue normally goes to needs-triage first; from there it moves to needs-info, ready-for-agent, ready-for-human, or wontfix. needs-info returns to needs-triage once the reporter replies. The maintainer can override at any time; flag transitions that look unusual and ask before proceeding.
Invocation
The maintainer invokes /triage and describes what they want in natural language. Interpret the request and act. Examples:
- "Show me anything that needs my attention"
- "Let's look at #42" (issue or PR)
- "Move #42 to ready-for-agent"
- "What's ready for agents to pick up?"
Show what needs attention
Query the issue tracker and present three buckets, oldest first:
- Unlabeled: never triaged.
needs-triage: evaluation in progress.needs-infowith reporter activity since the last triage notes: needs re-evaluation.
When PRs are in scope, include external PRs in these buckets and tag each line [PR] or [issue]. Discovery surfaces only external PRs (the tracker config defines who counts as external), so a collaborator's in-flight PR is not triage work. This filter is discovery-only; an explicitly named PR is always triaged regardless of author.
Show counts and a one-line summary per item. Let the maintainer pick.
Triage a specific issue or PR
Gather context. Read the full issue or PR (body, comments, labels, author, dates; for a PR, the diff too). Parse any prior triage notes so you don't re-ask resolved questions. Explore the codebase using the project's domain glossary, respecting ADRs in the area. Run two checks against the codebase: (a) redundancy: search for an existing implementation of the requested behavior by domain concept (not just the request's wording), and report where you looked. If found, it's an already-implemented
wontfix(step 5). (b) prior rejection: read.out-of-scope/*.mdand surface any that resembles this request.Recommend. Tell the maintainer your category and state recommendation with reasoning, plus a brief codebase summary relevant to the request (including whether it's already implemented). Wait for direction.
Verify the claim. Before any grilling, check that the claim holds up. For a bug, reproduce it from the reporter's steps. For a PR, confirm the diff does what it claims: check it out, run the relevant tests or commands. Report what happened: confirmed (with code path), failed, or insufficient detail (a strong
needs-infosignal). A confirmed verification makes a much stronger agent brief.Grill (if needed). If the request needs fleshing out, call the Skill tool twice, for "grilling" and "domain-modeling", and grill it into shape a round of questions at a time, sharpening domain terms and updating
GLOSSARY.md/ADRs inline as decisions land.Apply the outcome:
ready-for-agent: post an agent brief comment (AGENT-BRIEF.md).ready-for-human: same structure as an agent brief, but note why it can't be delegated (judgment calls, external access, design decisions, manual testing).needs-info: post triage notes (template below).- For
wontfix, close the issue, with the comment depending on why:- Already implemented: the change already exists in the codebase. Point to where it lives; do not write to
.out-of-scope/(that KB is for rejected requests, not built ones). - Rejected (bug): give a polite explanation, then close.
- Rejected (enhancement): write to
.out-of-scope/, link to it from a comment, then close (OUT-OF-SCOPE.md).
- Already implemented: the change already exists in the codebase. Point to where it lives; do not write to
needs-triage: apply the role. Optional comment if there's partial progress.
Quick state override
If the maintainer says "move #42 to ready-for-agent", trust them and apply the role directly. Confirm what you're about to do (role changes, comment, close), then act. Skip grilling. If moving to ready-for-agent without a grilling session, ask whether they want to write an agent brief.
Needs-info template
## Triage Notes
**What we've established so far:**
- point 1
- point 2
**What we still need from you (@reporter):**
- question 1
- question 2
Capture everything resolved during grilling under "established so far" so the work isn't lost. Questions must be specific and actionable, not "please provide more info".
Resuming a previous session
If prior triage notes exist on the issue or PR, read them, check whether the reporter has answered any outstanding questions, and present an updated picture before continuing. Don't re-ask resolved questions.
Connect through AnyModel API
This skill runs on whatever model your agent uses. Point Claude Code, Codex or Cursor at AnyModel to run it on Claude, GPT, Gemini and more with one key — pay per token, no subscription.
AnyModel