bug-diagnosis
Diagnose a bug systematically instead of guessing — reproduce, isolate, form hypotheses, and test them to root cause. Use when debugging, chasing a defect, an intermittent failure, or 'why is this happening?'. Produces a structured diagnosis: a reliable repro, the narrowed-down location, ranked hypotheses with how to test each, and the root cause + fix once found.
npx skills add mohitagw15856/pm-claude-skills --skill bug-diagnosis --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 Diagnosis Skill The slowest way to fix a bug is to start changing code and hope. This skill runs a disciplined diagnostic loop: **reproduce it reliably, isolate where it happens, hypothesize why, and test the cheapest hypothesis first** — narrowing until the root cause is proven, not guessed. It produces a fix *and* an explanation of why the bug existed. ## Required Inputs Ask for these only if they aren't already provided: - **The symptom** — what's wrong: expected vs. actual behavior, error/stack trace, when it started. - **Repro steps** — how to trigger it (or "can't reliably reproduce yet"). - **Context** — recent changes, environment, frequency (always / intermittent / specific inputs). - **What's been tried** — so we don't repeat dead ends. ## Output Format ### Diagnosis: [bug] **1. Reproduce** — the minimal, reliable steps to trigger it. If it's intermittent, the plan to make it deterministic (fixed input/seed, added logging, narrowed conditions). *No fixing until it reproduces.* **2. Isolate** — narrow *where* it happens: bisect (git bisect / comment-out / binary search the input), check the boundaries (what's the last known-good point vs. first bad). State the smalle
- Required Inputs
- Output Format
- Diagnosis: [bug]
- Quality Checks
- Anti-Patterns
- Based On
What does the bug-diagnosis skill do?
Diagnose a bug systematically instead of guessing — reproduce, isolate, form hypotheses, and test them to root cause. Use when debugging, chasing a defect, an intermittent failure, or 'why is this happening?'. Produces a structured diagnosis: a reliable repro, the narrowed-down location, ranked hypotheses with how to test each, and the root cause + fix once found.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill bug-diagnosis --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.