Bug Triage Pack
A bug backlog is only as good as its triage — and most bugs arrive as "it's broken" with no repro, a panicked severity, and no idea who should look. This turns a raw report into a triaged item: reproducible steps, a severity and priority you can defend (not vibes), the environment that matters, a suspected area and owner queue, and a check for whether it's a duplicate — asking for what's missing instead of inventing it.
What This Skill Produces
- Normalized repro — clear, numbered steps; expected vs. actual; the minimal path to reproduce
- Severity & priority — each with reasoning (impact × frequency × workaround availability), not a gut number
- Environment & metadata — version, platform, browser/OS, user/role, first-seen, frequency
- Suspected area & owner queue — where it likely lives and who should take it next
- Duplicate/related check — is this the same as a known issue, and what to link
- Missing-info flags — what the reporter must supply before it's actionable
Required Inputs
Ask for these if not provided:
- The raw report — whatever came in (a Slack message, a customer ticket, a screenshot description)
- Your severity/priority scale — what P0–P3 / S1–S4 mean here (else a sensible default is used and labelled)
- Environment details — version, platform, who hit it, how often
- Known issues (optional) — a list to dedupe against
Framework: Triage You Can Defend
- Repro or it's not a bug yet. No reliable steps → the first action is "needs repro," not a severity.
- Severity ≠ priority. Severity is how bad the impact is; priority is when we fix it (a rare-but-catastrophic bug and a constant-but-cosmetic one differ on both axes).
- Score, don't feel. Impact (data loss > broken flow > cosmetic) × frequency (all users > edge case) × workaround (none > easy) → a defensible level.
- Route it. Suspected component and the queue/owner it should go to — triage that doesn't route just moves the pile.
- Dedupe. Check against known issues; a linked duplicate is worth more than a fifth copy.
- Flag gaps, don't guess. Missing environment or repro is a request to the reporter, not an assumption.
Output Format
Bug: [title] · Severity [Sx] · Priority [Px]
Why this level: impact [x] × frequency [y] × workaround [z].
Repro
- … → Expected: … · Actual: …
Environment
| Version | Platform | User/role | First seen | Frequency |
Routing
- Suspected area: [component] · Suggested queue/owner: [team].
Duplicate / related
- [links, or "no known duplicate"].
⚠ Missing before it's actionable
- [what the reporter must add].
Quality Checks
Anti-Patterns
- A severity with no reasoning — "this is a P1" because it feels urgent.
- Conflating severity and priority — they answer different questions.
- Assigning a level without repro — triage a phantom and you fix nothing.
- No routing — a triaged bug with no owner queue is still stuck.
- Inventing environment/repro the reporter never gave.
Example Trigger Phrases
- "Triage this bug and set severity and priority: [paste]"
- "Is this a P1? Here's the report."
- "Clean up this bug for the backlog with repro steps and an owner."
- "Normalize this customer bug report and check if it's a duplicate."
1---2name: bug-triage-pack3description: "Triage a raw bug report into something a team can act on — clean repro steps, a defensible severity/priority, environment, likely area/owner, and duplicate check. Use when asked to triage this bug, set severity and priority, is this a P1, or clean up this bug report for the backlog. Produces the normalized repro, a severity and priority with the reasoning (impact × frequency × workaround), the environment/metadata, a suspected component and owner queue, and a duplicate/related-issue check — flagging when info is missing rather than guessing."4disable-model-invocation: true # skill-optimizer5metadata:6 source: https://skillmd.com/skills/slipcast-dev/bug-triage-pack7---89# Bug Triage Pack1011A bug backlog is only as good as its triage — and most bugs arrive as "it's broken" with no repro, a panicked severity, and no idea who should look. This turns a raw report into a triaged item: reproducible steps, a severity and priority you can defend (not vibes), the environment that matters, a suspected area and owner queue, and a check for whether it's a duplicate — asking for what's missing instead of inventing it.1213## What This Skill Produces1415- **Normalized repro** — clear, numbered steps; expected vs. actual; the minimal path to reproduce16- **Severity & priority** — each with reasoning (impact × frequency × workaround availability), not a gut number17- **Environment & metadata** — version, platform, browser/OS, user/role, first-seen, frequency18- **Suspected area & owner queue** — where it likely lives and who should take it next19- **Duplicate/related check** — is this the same as a known issue, and what to link20- **Missing-info flags** — what the reporter must supply before it's actionable2122## Required Inputs2324Ask for these if not provided:25- **The raw report** — whatever came in (a Slack message, a customer ticket, a screenshot description)26- **Your severity/priority scale** — what P0–P3 / S1–S4 mean here (else a sensible default is used and labelled)27- **Environment details** — version, platform, who hit it, how often28- **Known issues (optional)** — a list to dedupe against2930## Framework: Triage You Can Defend31321. **Repro or it's not a bug yet.** No reliable steps → the first action is "needs repro," not a severity.332. **Severity ≠ priority.** Severity is how bad the impact is; priority is when we fix it (a rare-but-catastrophic bug and a constant-but-cosmetic one differ on both axes).343. **Score, don't feel.** Impact (data loss > broken flow > cosmetic) × frequency (all users > edge case) × workaround (none > easy) → a defensible level.354. **Route it.** Suspected component and the queue/owner it should go to — triage that doesn't route just moves the pile.365. **Dedupe.** Check against known issues; a linked duplicate is worth more than a fifth copy.376. **Flag gaps, don't guess.** Missing environment or repro is a request to the reporter, not an assumption.3839## Output Format4041### Bug: [title] · **Severity [Sx]** · **Priority [Px]**42**Why this level:** impact [x] × frequency [y] × workaround [z].4344### Repro451. … → **Expected:** … · **Actual:** …4647### Environment48| Version | Platform | User/role | First seen | Frequency |4950### Routing51- Suspected area: [component] · Suggested queue/owner: [team].5253### Duplicate / related54- [links, or "no known duplicate"].5556### ⚠ Missing before it's actionable57- [what the reporter must add].5859## Quality Checks60- [ ] Repro steps are clear and include expected vs. actual (or "needs repro" is the flagged first action)61- [ ] Severity and priority are distinct and each justified by impact × frequency × workaround62- [ ] Environment/metadata is captured (or flagged missing)63- [ ] A suspected area and owner queue are proposed64- [ ] A duplicate/related check is done65- [ ] Missing information is requested, not invented6667## Anti-Patterns68- **A severity with no reasoning** — "this is a P1" because it feels urgent.69- **Conflating severity and priority** — they answer different questions.70- **Assigning a level without repro** — triage a phantom and you fix nothing.71- **No routing** — a triaged bug with no owner queue is still stuck.72- **Inventing environment/repro** the reporter never gave.7374## Example Trigger Phrases75- "Triage this bug and set severity and priority: [paste]"76- "Is this a P1? Here's the report."77- "Clean up this bug for the backlog with repro steps and an owner."78- "Normalize this customer bug report and check if it's a duplicate."