Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ibrahim-3d/systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Passed 14 of 21 test cases with the skill, and 15 of 21 without it.
1 fixed14 passed either way5 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
When attempting to debug a memory leak, a team member suggests 'Let us try changing memory settings or restarting threads and see what happens.' How should the hypothesis be stated before making changes?
| Checked | Without skill | With skill |
|---|---|---|
| Formulates a single explicit hypothesis stating cause and mechanism. | 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 15 / 21 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.