issue-triage

Installation
SKILL.md

Issue Triage

Triage decides, for each inbound issue or external pull request, what it is, whether it is real, whether the project wants it, and who makes the next move. The agent runs it as a state machine — new → needs-info → reproduced → accepted / duplicate / out-of-scope → ready-for-agent / ready-for-human — so every item has one owner of its next step and shortcuts become visible. A PR is an issue with code attached: same states, read against the diff.

When to Use

  • A backlog of unlabelled or needs-info issues needs clearing
  • Deciding whether a bug report holds up or a feature request is wanted
  • An external PR arrives and needs a verdict before review time is spent
  • An accepted issue is about to go to a coding agent and needs a brief

Clarify First

The tracker conventions and who decides shape every label change. Settle the inputs below before producing anything. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.

  • Label scheme and tracker: state may be labels or native statuses; mapping wrongly creates two sources of truth. Default: type:/state:/priority: labels.
  • Out-of-scope register location: without it, the prior-rejection check cannot run and old debates restart.
  • Who confirms decisions: the agent recommends; a maintainer approves state changes unless they said to apply them directly.
Installs
2
GitHub Stars
1.2K
First Seen
7 days ago