Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mohitagw15856/bug-diagnosis
Diagnose a bug systematically instead of guessing — reproduce, isolate, form hypotheses, and test them to root cause.
Passed 16 of 22 test cases with the skill, and 10 of 22 without it.
and 5 more in the full report
6 fixed10 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
Users are reporting that updating their profile details throws an unhandled '500 Internal Server Error' when entering unicode names like 'Renée'. It worked fine in staging. I haven't tried anything yet besides checking the Sentry log. Walk me through a rigorous debugging report: show how to reproduce this consistently, narrow down where the failure occurs, list ranked hypotheses in a comparison chart detailing cheap verification methods, confirm the root issue, and give me a fix with a test that fails initially and passes post-fix.
| Checked | Without skill | With skill |
|---|---|---|
| Includes section header '**1. Reproduce**' | Missed | Passed |
| Ranks hypotheses by evaluating high-probability and low-cost verification steps before expensive ones. | Passed | Passed |
| Requires a regression test that fails before the code fix and passes after it. | Passed | Passed |
The instructions your model reads when the skill loads.
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.
Ask for these only if they aren't already provided:
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 smallest scope that still shows the bug.
3. Hypotheses (ranked) — likely causes, most-probable-and-cheapest-to-test first:
| Hypothesis | Why plausible | How to test it (the cheap check) | Verdict |
|---|
Test them in order; record what each rules in or out.
4. Root cause — the proven cause (not a symptom), with the evidence that confirms it.
5. Fix & guard — the fix, a test that fails before it and passes after (lock the bug out), and any nearby instances of the same mistake.
test cases passed, vs 10 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.