borghei/Claude-Skills / project-management/execution/issue-triage
issue-triage
VerifiedMove engineering issues and external PRs through a triage state machine and write agent-ready briefs. Use when clearing a triage queue, deciding if a report is real or wanted, or handing an issue to a coding agent.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.4 KB |
| assets/agent_brief_template.md | markdown | 2.1 KB |
| assets/label_scheme_template.md | markdown | 2.7 KB |
| assets/out_of_scope_entry_template.md | markdown | 1.6 KB |
| assets/sample_agent_brief_clean.md | markdown | 2.6 KB |
| assets/sample_agent_briefs.json | config | 2.8 KB |
| assets/sample_triage_history.json | config | 3.7 KB |
| assets/sample_triage_history_clean.json | config | 3.4 KB |
| assets/triage_notes_template.md | markdown | 2.1 KB |
| references/agent-briefs.md | markdown | 10.3 KB |
| references/evidence-and-out-of-scope.md | markdown | 9.2 KB |
| references/state-machine-and-labels.md | markdown | 10.4 KB |
| scripts/agent_brief_linter.py | script | 10.1 KB |
| scripts/triage_state_validator.py | script | 12.6 KB |
assets/label_scheme_template.md
View on GitHub# Label Scheme Template
Copy into the repository's contributing docs and create the labels once.
The prefixes are what `triage_state_validator.py` reads; the tracker column
shows how to express each one where labels are not the native mechanism.
## Invariants
- Exactly one `type:` label on every triaged item.
- Exactly one `state:` label on every item, matching its last transition.
- At most one `priority:` label; required from `state:accepted` onward.
- Area/component labels are free-form and unlimited.
## Type labels
| Label | Meaning |
|---|---|
| `type:bug` | Existing behaviour is wrong. Must pass through `reproduced` before `accepted`. |
| `type:enhancement` | New capability or a change to intended behaviour. |
| `type:chore` | Maintenance with no user-visible change (deps, CI, refactor). |
| `type:docs` | Documentation only. |
| `type:question` | Usage question; usually answered and closed, or converted. |
## State labels
| Label | Meaning | Owner of next move |
|---|---|---|
| `state:new` | Not yet evaluated | Triager |
| `state:needs-info` | Waiting on the reporter | Reporter |
| `state:reproduced` | Bug confirmed / PR diff verified | Triager |
| `state:accepted` | We want it; not yet specified for hand-off | Triager |
| `state:ready-for-agent` | Brief posted; a coding agent may take it | Agent |
| `state:ready-for-human` | Brief posted; needs a person (reason stated) | Maintainer |
| `state:duplicate` | Closed; points at the canonical issue | — |
| `state:out-of-scope` | Closed; recorded in the out-of-scope register | — |
| `state:already-implemented` | Closed; points at where it already exists | — |
| `state:stale-closed` | Closed after the needs-info close window | Reporter can reopen |
| `state:resolved` | Fixed or merged | — |
## Priority labels
| Label | Rule of thumb |
|---|---|
| `priority:p0` | Data loss, security, or outage. Interrupts current work. |
| `priority:p1` | Broken core path for many users; next in line. |
| `priority:p2` | Real but contained; scheduled normally. |
| `priority:p3` | Nice to have; taken when convenient. |
## Tracker mapping
| Concept | GitHub | GitLab | Linear | Jira |
|---|---|---|---|---|
| type | label `type:*` or issue type | scoped label `type::*` | label group "Type" | Issue type |
| state | label `state:*` | scoped label `state::*` (enforces one) | workflow status | workflow status |
| priority | label `priority:*` | scoped label `priority::*` | native priority | Priority field |
| duplicate link | "Duplicate of #n" comment / close reason | "Duplicate of" link | Mark as duplicate | "duplicates" link |
| PR in triage | PR with the same labels | MR with the same labels | linked PR on the issue | linked PR / dev panel |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Unverified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |