Use bug-triage

Turn a vague bug report (Slack message, support ticket, "it's broken on mobile sometimes") into an actionable ticket

Turn a vague bug report (Slack message, support ticket, "it's broken on mobile sometimes") into an actionable ticket — searchable symptom title, numbered repro steps from a clean state, expected vs actual, severity separated from priority, evidence tagged reported-vs-verified, and labeled hypotheses instead of root-cause guesses.

Reach for it when the user wants to triage a bug, write up a bug report, turn a complaint into a ticket, or make a flaky issue actionable.

Install it

npx skilldrop-cli install bug-triage                 # Claude Code, your user folder
npx skilldrop-cli install bug-triage --project       # Claude Code, this repo
npx skilldrop-cli install bug-triage --ide cursor    # or kiro, codex, antigravity, copilot

It is part of the Dev team pack: --pack dev-team installs it with its neighbours.

Ask for it

Say it the way you would to a colleague. Requests like these route to it:

"Turn this vague bug report into an actionable ticket"
"A customer says it's broken on mobile sometimes — triage it"
"Write up this Slack complaint as a proper bug with repro steps"
"Triage and prioritize this support ticket"

Requests like these belong to a different skill, so it shouldn't answer them:

"Review this diff for bugs and edge cases"
"Write the blameless postmortem for the outage"
"Split this epic into user stories"

If another skill answers instead, ask for this one by name: "use bug-triage".

Check what you get

A good result:

An engineer can start without contacting the reporter. Either the repro stands alone or the no-repro diagnostics list says exactly what to collect.
Title findable by symptom search. If the words a future reporter would type don't appear in it, retitle.
Zero untagged claims. Every factual statement is [reported], [verified], or [assumption] — a triager's authority comes from the tags.
Severity and priority each have a stated reason, and they were judged independently — one line each, no shared justification.
Hypotheses ≤ 3, each with a concrete check. A hypothesis without a check is a vibe.
The verbatim error text is present when any error was shown — quoted exactly, not paraphrased.

Use something else when

Actually fixing the bug — hand the ticket to feature-implement-loop or a human
A production incident in progress — mitigate first; this is queue work, not response work
The post-incident analysis — that's postmortem-generator
A feature request wearing a bug costume ("bug: there's no dark mode") — route to user-story-splitter

Where a loop runs it

Stage shape of the build loop

SKILL.md, the instructions the agent reads
Its page on the site
Related: feature-implement-loop, postmortem-generator, user-story-splitter

Edit this page on GitHub · View source