Debugging
A battle-tested Claude Code skill collection that enforces Plan→Execute→Verify→Handoff workflow. Auto-triggers brainstorming, planning, debugging, UI/UX, security, and review skills.
npx -y skills add kjhk3082/master-assistant-skill --skill debuggingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
[EN] You MUST use this when investigating errors, bugs, or unexpected behavior. Provides a systematic approach to root cause analysis. [KO] 에러, 버그 또는 예기치 않은 동작을 조사할 때 반드시 사용해야 합니다. 근본 원인 분석에 대한 체계적인 접근 방식을 제공합니다.
SKILL.md
1.3 KB, 221 tokens by cl100k_base, as published. Nobody here has run it
Systematic Debugging
A structured approach to finding and fixing bugs.
<HARD-GATE> Do NOT guess or immediately change code when an error occurs. You MUST follow the systematic debugging process to find the root cause first. </HARD-GATE>The 4-Phase Debugging Process
-
Reproduce & Isolate
- Confirm the exact error message or behavior
- Identify the minimal steps to reproduce
-
Root Cause Tracing
- Trace the execution path backwards from the error
- Add temporary logging if necessary
- Formulate a hypothesis about the root cause
-
Verify Hypothesis
- Test the hypothesis (e.g., by checking variable values)
- Do NOT proceed to fixing until the hypothesis is confirmed
-
Fix & Verify
- Apply the minimal necessary fix
- Run tests or manually verify the fix resolves the issue without breaking other things
- Document the fix in
docs/wiki/gotchas.mdif it's a recurring issue or tricky edge case