Triage

Triage reviews issue evidence, moves work through repository-specific states and prepares a brief when an agent can take the next step.

Decide what should happen to one issue

Gather evidence for the issue before assigning a category or state. Keep the proposed tracker update separate from the review.

Which issue or PR needs triage?

Provide its URL, repository conventions and any attempted reproduction.

Copy the request into a new Floatboat conversation and provide the required material.

Download Floatboat

Your request for Floatboat

Preview and copy the request. It is not sent automatically from this page.

Reference: Triage
https://github.com/mattpocock/skills/blob/main/skills/engineering/triage/SKILL.md

Read the original documentation and check the current environment and dependencies. Propose any new installation or tool connection before proceeding.

My task:
Use Matt Pocock’s Triage on issue #42. Check the reproduction, related code and prior decisions. Recommend one category and state, and draft an agent brief if evidence is sufficient. Do not post until I approve.

Expected deliverable:
A reasoned state recommendation with an agent brief or one targeted follow-up question.

What Triage does

Matt Pocock’s Triage Skill gives an issue one category and one state. It looks at the report, code, domain glossary and previous decisions before recommending whether to request more evidence, prepare a brief, assign human work or close the request. External pull requests join the queue when the repository enables that surface. Setup Matt Pocock Skills provides the tracker and label mapping.

Triage use cases

An issue is ready for an agent when the expected behavior and verification are clear. If the evidence cannot support that decision yet, record the missing detail and who can provide it.

Ask for a useful reproduction

When a bug report lacks a revision or expected result, identify the single piece of evidence that would unblock diagnosis and prepare a focused request for the reporter.

Catch an already implemented request

Search by domain concept, not just the wording of the issue. Record where the behavior already exists and propose closure with evidence a maintainer can inspect.

Prepare bounded work for an agent

When behavior and scope are clear, write a brief with the relevant files, expected result and validation. Include what the agent must leave unchanged so the assignment is reviewable.

Route an external pull request

If external PR triage is enabled, inspect the diff and checks alongside its description. Separate a small agent follow-up from the human decision to accept or merge the change.

How to use Triage

Choose one issue or PR and load the repository’s role mapping. Present the evidence, recommended state and draft comment separately so the maintainer can review each before any tracker update.

Load the tracker and labels
Read the repository’s configuration and confirm which issue or PR should be reviewed.
Gather evidence before assigning a state
Read the thread and related code. Check for conflicting labels, an existing implementation, prior decisions and missing evidence.
Show the proposed update
Present the category, state and brief or follow-up question. Apply approved changes through the configured tracker.

Explore More Agent Skills

Read another Skill guide and check its original source before using it.

Triage FAQ

What is the difference between category and state?

The category describes whether the request is a bug or enhancement. The state says what needs to happen next and who can act.

What if the issue has conflicting states?

The upstream Skill calls for flagging conflicting states and asking a maintainer before proceeding with changes.

Do I need to configure the repository first?

Triage expects the tracker and role mapping. Run Setup Matt Pocock Skills if those references are missing.

Can it review external PRs?

Yes, when the repository’s configuration enables that request surface. Its default discovery also distinguishes external contributors from collaborators.

What belongs in an agent-ready brief?

Record the intended behavior, supporting evidence and clear checks. Flag open design decisions that still require human input.

Will a Triage comment identify its source?

The upstream instructions require an AI-triage disclosure on comments or issues it posts. Review and authorize any external update first.