Individual skill
systematic-debugging
You MUST use this whenever something is broken, before proposing or making any fix, including quick fixes and when the user is in a hurry: a bug, a failing or red test, a build or CI failure, a crash, a performance problem, unexpected behavior. Finds the root cause in four phases (investigate, compare, test one hypothesis, fix with a failing test first) instead of guessing, and stops after three failed fixes to question the design. Not for writing new features.
cli-tool/components/skills/development/systematic-debugging/SKILL.md
Source commit ad81bf053f80b626801decf425f501ba49983d98
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 33,193
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- anthropic Repository topic
- anthropic-claude Repository topic
- claude Repository topic
- claude-code Repository topic
- agent-skills Repository topic
- ai-agents Repository topic
- claude-code-plugins Repository topic
- cli Repository topic
- mcp Repository topic
- registry Repository topic
- testing Derived category
- design Derived category
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
LICENSEasset · 1,070 bytesSKILL.mdcore · 9,553 bytesSKILL.mdcore · 9,553 bytesSKILL.mdcore · 9,553 bytesreferences/condition-based-waiting-example.tsruns · 5,054 bytesreferences/condition-based-waiting.mddoc · 3,767 bytesreferences/defense-in-depth.mddoc · 3,665 bytesreferences/root-cause-tracing.mddoc · 5,546 bytesscripts/find-polluter.shruns · 3,491 bytes
Read excerpt
# Systematic Debugging
Guessing at fixes feels fast and is slow. Each guess that half-works hides
the real cause a little deeper, and the third patch usually breaks
something the first one touched. This skill makes you find out *why*
before you change anything.
## The Iron Law
```
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
```
If you have not finished Phase 1, you cannot propose a fix. Not a "quick