Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions. Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill systematic-debuggingOverall
score
84%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 92%
↑ 1.16xAgent success when using this skill
Validation for skill structure
Multi-component diagnostic instrumentation
Pre-fix instrumentation
7%
87%
Boundary data logging
33%
83%
Layer identification from evidence
70%
100%
Root cause not symptom
100%
100%
No symptom-layer fix
100%
100%
Single focused fix
100%
100%
Evidence-first run
0%
86%
Investigate-then-fix sequence
38%
92%
Fix verification
100%
100%
Single component changed
100%
100%
Test-first hypothesis-driven fix
Test file exists
100%
100%
Test targets the bug
100%
100%
Test written before fix
29%
57%
Single documented hypothesis
100%
100%
Hypothesis identifies root cause
100%
100%
Bun as test runner
0%
0%
Minimal single fix
92%
100%
countBusinessDays unchanged
100%
100%
No bundled improvements
100%
100%
Fix verified
70%
70%
Complete reference reading and difference listing
Comparison document exists
100%
100%
Loop boundary difference found
100%
100%
Sleep-after-last-failure found
100%
100%
Both differences documented
100%
100%
Behavioral impact explained
100%
100%
Analysis precedes fix
100%
100%
Loop boundary fixed
100%
100%
Sleep guard fixed
100%
100%
No extra changes
100%
100%
Fix matches reference
100%
100%
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.