Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →taracodlabs/systematic-debugging
Four-phase root cause investigation for bugs and unexpected behavior
Passed 17 of 22 test cases with the skill, and 12 of 22 without it.
and 2 more in the full report
5 fixed12 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
After applying a single-line bug fix and verifying that the original reproduction steps no longer fail, what immediate testing requirement must be satisfied before closing the ticket?
| Checked | Without skill | With skill |
|---|---|---|
| The verification phase specifies running the full test suite to check for regressions. | Missed | Passed |
The instructions your model reads when the skill loads.
A structured four-phase process for diagnosing software bugs: Reproduce → Isolate → Hypothesize → Verify. Prevents guessing and ensures you find the root cause, not just a workaround.
A bug you can reproduce consistently is halfway solved.
1. Get the exact error message, stack trace, and environment
2. Identify exact steps to trigger the bug
3. Confirm the bug happens in a clean environment (not just local state)
4. Record: OS, runtime version, dependencies, config values
5. Try: does it fail on every run, or only sometimes?
If intermittent: add timing, logging, or retry logic to isolate the trigger.
Narrow the failure to the smallest possible unit.
1. Add logging before/after suspected areas to find where state diverges
2. Binary search through code: comment out half, does it still fail?
3. Check: when did this last work? (git log, git bisect)
4. Check: what changed recently? (git diff main, dependency updates)
5. Reproduce in a minimal test case — strip away all unrelated code
test cases passed, vs 12 / 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.