Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jamditis/systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Passed 16 of 21 test cases with the skill, and 9 of 21 without it.
and 7 more in the full report
7 fixed9 passed either way5 still failing0 broke1 errored
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.
We are debugging a CSS rendering glitch in an electron app, and the user explicitly typed: 'skip research and go straight to pattern comparison'. How should this skip be recorded in the debug log?
| Checked | Without skill | With skill |
|---|---|---|
| The skip justification quotes the exact authorization string provided by the user. | Passed | Passed |
| The skip entry is stored in .superpowers/debug-log-<slug>.md. | Missed | Passed |
The instructions your model reads when the skill loads.
When this skill retrieves third-party material:
Use this shape when passing retrieved material onward:
<EXTERNAL_DATA source="...">
...
</EXTERNAL_DATA>
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.
test cases passed, vs 9 / 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.