arda/skills
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Swapped 'backlog' for 'issue tracker

Browse source 
Co-authored-by: Copilot <copilot@github.com>
This commit is contained in:
Matt Pocock 2026-04-28 19:06:32 +01:00
parent 5fed805a92
commit 179a14e721
11 changed files with 67 additions and 41 deletions
Download patch file Download diff file Expand all files Collapse all files

10
skills/engineering/triage/SKILL.md
View file

@ -1,13 +1,13 @@
---
name: triage
description: Triage backlog 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.
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.
---
# Triage
Move issues on the project backlog through a small state machine of triage roles.
Move issues on the project issue tracker through a small state machine of triage roles.
Every comment or issue posted to the backlog during triage **must** start with this disclaimer:
Every comment or issue posted to the issue tracker during triage **must** start with this disclaimer:
```
> *This was generated by AI during triage.*
@ -35,7 +35,7 @@ Five **state** roles:
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 on the backlog may differ. The mapping should have been provided to you - run `/setup-matt-pocock-skills` if not.
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.
@ -50,7 +50,7 @@ The maintainer invokes `/triage` and describes what they want in natural languag
## Show what needs attention
Query the backlog and present three buckets, oldest first:
Query the issue tracker and present three buckets, oldest first:
1. **Unlabeled** — never triaged.
2. **`needs-triage`** — evaluation in progress.