AGENT SKILL

triage

Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

License 许可
MIT
最近更新
2026-07-07
Stars
★ 1
Forks
0

01 前言 Front Matter

name
triage
license
MIT
metadata
{ "source": "Adapted from mattpocock/skills (MIT)", "disable-model-invocation": true }
description
Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.
compatibility
opencode

03 SKILL.md 正文

Tool mapping (OpenCode): This skill uses:

  • question tool for user prompts
  • task tool for subagents
  • skill({ name: "..." }) to load other skills
  • codegraph_explore, codegraph_search for codebase exploration (preferred)
  • grep, glob, read, bash as fallback
  • gh CLI for GitHub issue management

Context rule: This skill supersedes any prior skill instructions. Follow ONLY these instructions now.

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, triage covers them too: a PR is an issue with attached code — same roles, same states, same machine, with a few deltas marked "for a PR" below.

Every comment or issue posted to the issue tracker during triage must start with this disclaimer:

> *This was generated by AI during triage.*

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

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.

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:

  1. Unlabeled — never triaged.
  2. needs-triage — evaluation in progress.
  3. needs-info with reporter activity since the last triage notes — needs re-evaluation.

Show counts and a one-line summary per item. Let the maintainer pick.

Triage a specific issue or PR

  1. 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 — check if this request was previously rejected.

  2. 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.

  3. 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-info signal). A confirmed verification makes a much stronger agent brief.

  4. Grill (if needed). If the request needs fleshing out, invoke skill({ name: "grill-me" }) — grill it into shape one question at a time, sharpening domain terms and updating CONTEXT.md/ADRs inline as decisions land.

  5. Apply the outcome:

    • ready-for-agent — post an agent brief comment (concise, actionable, with acceptance criteria).
    • 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).
    • wontfix — close, with the comment depending on why:
      • Already implemented — point to where it lives.
      • Rejected (bug) — polite explanation, then close.
      • Rejected (enhancement) — explain rationale, then close.
    • 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.

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.

NEVER

  • NEVER triage without reading the full issue/PR first Instead: Read body, comments, labels, and any prior triage notes before making recommendations. Why: Surface-level triage asks already-answered questions and loses reporter trust.

  • NEVER skip the redundancy check Instead: Search for existing implementations before recommending new work. Why: Implementing something that already exists is the most common waste of agent time.

  • NEVER post to the issue tracker without the AI disclaimer Instead: Start every comment with > *This was generated by AI during triage.* Why: Transparency about AI-generated content builds trust with reporters.

04 同仓库更多 Skills