Agent skill · operations · mattpocock
triage
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
Why this skill is useful
Provides a structured workflow for triaging issues and PRs, including specific roles and state transitions that the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-06. 207,363 stars on the source repository.
What this skill does
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: 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 broken enhancement: new feature or improvement Five state roles: needs-triage: maintainer needs to evaluate needs-info: waiting on reporter for more information ready-for-agent: fully specified, ready for an AFK agent ready-for-human: needs human implementation wontfix: 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills mattpocock/triage