Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jamestorrevillas/debugging-mindset
Use this skill when debugging code, diagnosing unexpected behavior, troubleshooting errors, or approaching a problem systematically. Trigger on keywords: debug, bug, error, not working, unexpected behavior, troubleshoot, investigate, root cause, why is this, something is wrong, failing test, crash.
Passed 13 of 22 test cases with the skill, and 14 of 22 without it.
0 fixed13 passed either way8 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
The instructions your model reads when the skill loads.
Debug the system, not your assumptions.
Most bugs persist because developers debug what they think is happening instead of what's actually happening. Every assumption is a potential hiding place for a bug.
1. OBSERVE — What exactly is the symptom? (not interpretation, raw facts)
2. HYPOTHESIZE — What are the possible causes?
3. TEST — Design the smallest possible test to confirm/deny each hypothesis
4. CONCLUDE — What does the evidence tell you?
5. FIX — Address the root cause, not the symptom
6. VERIFY — Confirm the fix works and nothing else broke
7. PREVENT — Add a test that would catch this regression
Never skip step 7. Every bug is a test that doesn't exist yet.
Before writing a single line of debug code, answer these:
Answering these five questions often reveals the bug before you even look at code.
test cases passed, vs 14 / 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.