# Triage

Triage issues through a state machine driven by triage roles.

- Repository: https://github.com/stevesolun/ctx (589 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-10-14
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add stevesolun/ctx --skill triage -g -a claude-code -y`
Codex: `npx skills add stevesolun/ctx --skill triage -g -a codex -y`
Cursor: `npx skills add stevesolun/ctx --skill triage -g -a cursor -y`
Gemini CLI: `npx skills add stevesolun/ctx --skill triage -g -a gemini-cli -y`

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

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Triage

Move issues on the project issue tracker through a small state machine of triage roles.

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

```
> *This was generated by AI during triage.*
```

## Reference docs

- [AGENT-BRIEF.md](AGENT-BRIEF.md), how to write durable agent briefs
- [OUT-OF-SCOPE.md](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

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 - run `/setup-matt-pocock-skills` if not.

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"
- "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:

The rest: https://github.com/stevesolun/ctx/blob/HEAD/imported-skills/mattpocock/triage/SKILL.md