triage
Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- triage
- description
- Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
02 资源文件 2
- 参考文档AGENT-BRIEF.md6.1 KB
- 参考文档OUT-OF-SCOPE.md4.2 KB
03 SKILL.md 正文
Triage
Move issues on the project issue tracker through a small state machine of triage roles.
AI disclosure (opt-in)
If the project requires it (e.g. public open-source repos), prepend each comment posted during triage with:
> *This was generated by AI during triage.*
For internal or solo-maintained repos, skip the disclaimer unless the user asks for it.
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
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. If the project hasn't established a mapping, ask the maintainer once and remember it for the session.
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.
Issue tracker detection
Infer from the repo before asking:
.github/directory orgh repo viewsucceeds → GitHub Issueslinear.appreferences → Linear.scratch/markdown convention → markdown files
For ambiguous cases, ask the maintainer once where issues live.
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"
- "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.
Show counts and a one-line summary per issue. Let the maintainer pick.
Triage a specific issue
-
Gather context. Read the full issue (body, comments, labels, reporter, dates). 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. Read
.out-of-scope/*.mdif it exists and surface any prior rejection that resembles this issue. -
Recommend. Tell the maintainer your category and state recommendation with reasoning, plus a brief codebase summary relevant to the issue. Wait for direction.
-
Reproduce (bugs only). Before any grilling, attempt reproduction: read the reporter's steps, trace the relevant code, run tests or commands. Report what happened — successful repro with code path, failed repro, or insufficient detail (a strong
needs-infosignal). A confirmed repro makes a much stronger agent brief. -
Grill (if needed). If the issue needs fleshing out, run a
/grill-with-docssession. -
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).wontfix(bug) — polite explanation, then close.wontfix(enhancement) — write to.out-of-scope/, link to it from a comment, then close (OUT-OF-SCOPE.md).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, read them, check whether the reporter has answered any outstanding questions, and present an updated picture before continuing. Don't re-ask resolved questions.
04 同仓库更多 Skills
zoom-out
Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.
write-a-skill
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
symbol-surgery
Symbol-first refactoring discipline using the native LSP tool — locate by symbol, check blast radius before changing, edit at symbol boundaries, verify references after. Use when renaming, changing a signature, moving/extracting/inlining, or deleting code that other code depends on; or whenever the question is "where is this used and what breaks if I change it?" Mechanical-execution complement to `deepen` (which decides what to refactor) and `simplify` (which decides what's clean).
ship
Deploy, release, or run migrations against production for a project. Use when user says "deploy", "ship", "push to prod", "release", "run the migration", "apply migrations", or asks how a project gets deployed / where it lives. Reads per-project DEPLOY.md as source of truth; falls back to inference + offer to scaffold one.
session-closeout
Preserve durable lessons and produce an archive-safety receipt before ending, clearing, or archiving an agent task. Use without being asked when a task reaches its finish line (its PR merged and its worktree removed, or the deliverable handed over), and when the operator says close out, wrap up, end the session, prepare the task for archive, make it archive-ready, or invokes $session-closeout after substantive work.