Systematic Debugging
Use for ANY bug, test failure, or unexpected behavior. Use BEFORE proposing fixes. Four phases: investigate, analyze, hypothesize, implement. Ensures understanding before attempting solutions.
Install
/plugin marketplace add Freddy-CHEN-ux/00_claude_skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Freddy-CHEN-ux/00_claude_skills --skill systematic-debugginggit clone --depth 1 https://github.com/Freddy-CHEN-ux/00_claude_skills.git /tmp/00_claude_skills
mkdir -p ~/.claude/skills
cp -r /tmp/00_claude_skills/skills/systematic-debugging ~/.claude/skills/systematic-debuggingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Systematic Debugging
Find root cause before fixing.
> **Announce:** "I'm using systematic-debugging to investigate this issue before proposing fixes."
## Iron Law
```
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
```
If you haven't completed Phase 1, you cannot propose fixes.
## The Four Phases
You MUST complete each phase before proceeding to the next.
### Phase 1: Root Cause Investigation
**1.1 Read Error Messages Carefully**
- Don't skip past errors
- Read complete stack traces
- Note file paths, line numbers, error codes
**1.2 Reproduce Consistently**
- Can you trigger it reliably?
- What are exact steps?
- If not reproducible → gather more data, don't guess
**1.3 Check Recent Changes**
```bash
git log --oneline -10
git diff HEAD~5
```
- What changed that could cause this?
- New dependencies? Config changes?
**1.4 Gather Evidence**
For multi-component issues, trace the data flow:
```
Component A → Component B → Component C
↓ ↓ ↓
Log input Log input Log input
Log output Log output Log output
```
Add diagnostic logging at each boundary to find WHERE it breaks.
### Phase 2: Pattern Analysis
**2.1 Find Working Examples**
- Locate similar working code in codebase
- What's different between working and broken?
**2.2 Compare Against References**
- Read relevant specs: `openspec show [capability]`
- Check documentation for expected behavior
**2.3 Identify Differences**
- List EVERY difference, however smallDetails
- Skill name
systematic-debugging- Repository
- Freddy-CHEN-ux/00_claude_skills
- Path
skills/systematic-debugging/SKILL.md- Repo updated
- 10 January 2026
FAQ
What does the Systematic Debugging skill do?
Use for ANY bug, test failure, or unexpected behavior. Use BEFORE proposing fixes. Four phases: investigate, analyze, hypothesize, implement. Ensures understanding before attempting solutions.
How do I install the Systematic Debugging skill?
Claude Code plugin: /plugin marketplace add Freddy-CHEN-ux/00_claude_skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Systematic Debugging popular?
It lives in Freddy-CHEN-ux/00_claude_skills, which has 8 GitHub stars and 3 forks.
Related skills
Add Integration
8Freddy-CHEN-ux/00_claude_skills
Build a new API integration for Nexus. Load when user mentions "add integration", "new integration", "integrate with", "connect to [service]", or "build [service] integration". Interactive workflow that discovers API endpoints, plans the integration, and creates a project for implementation.
AI Agents
8Freddy-CHEN-ux/00_claude_skills
Production-grade AI agent patterns with MCP integration, agentic RAG, handoff orchestration, multi-layer guardrails, and observability (modern best practices)
AI LLM
8Freddy-CHEN-ux/00_claude_skills
Production LLM engineering skill. Covers strategy selection (prompting vs RAG vs fine-tuning), dataset design, PEFT/LoRA, evaluation workflows, deployment handoff to inference serving, and lifecycle operations with cost/safety controls.
Test Driven Development
8Freddy-CHEN-ux/00_claude_skills
Use when adding features or fixing bugs. Follow RED/GREEN/REFACTOR cycle. Write failing test first, implement minimal code to pass, then refactor.
Systematic Debugging
8Freddy-CHEN-ux/00_claude_skills
Use when encountering bugs or unexpected behavior. Methodical approach to identify root cause: Reproduce → Isolate → Identify → Fix → Verify.
Tidy First
5vnovakovits/claude-skills
Apply Kent Beck's "Tidy First?" approach — small structure changes (tidyings) separated from behavior changes, sequenced as "first / after / later / never", informed by software design as an economic activity (coupling, cohesion, optionality, discount rate). Use when about to make a behavior change in messy code, when reviewing a tangled PR, when deciding whether to clean up now or later, or when thinking about software design as a long-running investment decision rather than a craft aesthetic.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.