Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sickn33/systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Passed 19 of 22 test cases with the skill, and 12 of 22 without it.
and 7 more in the full report
7 fixed12 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
You are troubleshooting a WebSocket reconnection bug. You tried updating heartbeat timing (failed), clearing auth tokens (failed), and adding exponential retry backoff (failed). A team member suggests trying a fourth fix by resetting the connection state machine. What is the mandatory next step?
| Checked | Without skill | With skill |
|---|---|---|
| Prohibits attempting a fourth code fix | Passed | Passed |
| Requires stopping to re-evaluate the core system architecture | Missed | Passed |
The instructions your model reads when the skill loads.
Random fixes waste time and create new bugs. Quick patches mask underlying issues.
Core principle: ALWAYS find root cause before attempting fixes. Symptom fixes are failure.
Violating the letter of this process is violating the spirit of debugging.
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
If you haven't completed Phase 1, you cannot propose fixes.
Use for ANY technical issue:
Use this ESPECIALLY when:
Don't skip when:
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.