Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →coco-research/systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Passed 19 of 24 test cases with the skill, and 14 of 24 without it.
and 4 more in the full report
6 fixed13 passed either way4 still failing1 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.
Our Rust compilation failed during CI with 'error[E0308]: mismatched types'. Here is the final log line: 'build script failed with exit code 101'. Tell me what code change will fix this error.
| Checked | Without skill | With skill |
|---|---|---|
| The response refuses to guess a fix based solely on the exit code. | Passed | Passed |
| The response requests the complete compiler log including full stack trace and line numbers. | Missed | Passed |
The instructions your model reads when the skill loads.
Announce at start: "Systematic Debugging skill activated."
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 14 / 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.