1.7 KiB
Triage Labels
The skills use canonical roles. This file maps those roles to the actual Gitea label strings for tararar/Aleksandr-test.
State roles
| Label in mattpocock/skills | Label in our tracker | Meaning |
|---|---|---|
| needs-triage | needs-triage | Maintainer needs to evaluate the issue |
| needs-info | needs-info | Waiting on the reporter for more information |
| ready-for-agent | ready-for-agent | Fully specified and ready for an AFK agent |
| ready-for-human | ready-for-human | Requires human implementation |
| wontfix | wontfix | Will not be actioned |
Category roles
| Canonical role | Label in our tracker | Meaning |
|---|---|---|
| bug | bug | Something is broken |
| enhancement | enhancement | New feature or improvement |
Rules
Every triaged issue must carry exactly one category label and exactly one state label. Preserve unrelated labels.
If multiple state labels conflict, flag the conflict and ask the maintainer before changing anything.
Use these mapped strings whenever a skill refers to a canonical role.
The normal state path starts at needs-triage and proceeds to needs-info, ready-for-agent, ready-for-human, or wontfix. Once the reporter supplies the requested information, needs-info returns to needs-triage for re-evaluation.
Follow the installed triage skill for verification, recommendations, agent briefs, closure, and recording rejected enhancements.
Every issue or comment posted during triage must begin with:
This was generated by AI during triage.
Check Gitea for existing labels before creating missing ones. This configuration file defines the vocabulary; writing it does not itself create labels on the server.