Individual skill
systematic-debugging
4-phase root cause analysis: observe, hypothesize, verify, fix. Enforces investigation before any code changes. Emergency stop after 2 failed fixes. Prevents shotgun debugging and fix cascades.
skills/systematic-debugging/SKILL.md
Source commit e1a3d45697a0f323aaedcbea0ab6a0387b5fe722
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- 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)
- 927
- Repository last updated
- Nov 5, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-orchestration Repository topic
- agent-workflow Repository topic
- ai-agents Repository topic
- claude-code-plugin Repository topic
- claude-plugins Repository topic
- codex-plugin Repository topic
- developer-tools Repository topic
- mcp Repository topic
- testing 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
SKILL.mdcore · 5,449 bytesSKILL.mdcore · 5,449 bytes__benchmarks__/no-error-info.mddoc · 771 bytes__benchmarks__/with-error.mddoc · 907 bytes
Read excerpt
# /systematic-debugging — Root Cause Before Fix
## Orientation
**Use when:** root cause is unknown and premature fixes keep failing -- enforces observe -> hypothesize -> verify before touching code.
**Don't use when:** root cause is already known (use /marshal to implement the fix); the bug is shallow and the stack trace is enough (use /do).
## Protocol
### Phase 1: OBSERVATION & REPRODUCTION
1. Read the error message, stack trace, or bug description
2. Reproduce the issue:
- If it's a type error: run typecheck and read the full error