Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →dicklesworthstone/systematic-debugging
Structured approach to finding and fixing bugs
Passed 24 of 24 test cases with the skill, and 18 of 24 without it.
and 7 more in the full report
6 fixed18 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am adding temporary debug logging across `auth_service.py` to trace why authentication headers are missing. What information elements should be included in each log line, and what action must be taken before committing?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends including location, variable name, value, and timestamp in debug log statements. | Missed | Passed |
| Mandates removing temporary debug logs before committing. | Passed | Passed |
The instructions your model reads when the skill loads.
REPRODUCE → ISOLATE → TRACE → FIX → VERIFY
Never skip steps. Never guess.
Goal: See the bug happen reliably
1. Get exact reproduction steps
2. Run them yourself
3. See the exact error
4. Document: input, output, expected
Red flags:
Goal: Find minimum case that shows bug
1. Start removing things
2. Does bug still happen?
3. Keep removing until minimal
4. Result: smallest repro case
Why this matters:
test cases passed, vs 18 / 24 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.