bug-triage-pack
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.
npx skills add mohitagw15856/pm-claude-skills --skill bug-triage-pack --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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/p
- What This Skill Produces
- Required Inputs
- Framework: Triage You Can Defend
- Output Format
- Bug: [title] · Severity [Sx] · Priority [Px]
- Repro
- Environment
- Routing
- Duplicate / related
- ⚠ Missing before it's actionable
- Quality Checks
- Anti-Patterns
- Example Trigger Phrases
What does the bug-triage-pack skill do?
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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill bug-triage-pack --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.