Systematic Debugging

Disciplined methodology to isolate bugs through hypothesis-driven testing. Form hypotheses, test them with minimal changes, narrow scope systematically. Use when bugs are unclear or reproduce intermittently.

48 stars 10 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill systematic-debugging
Manual install
git clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/engineer/debugging/skills/systematic-debugging ~/.claude/skills/systematic-debugging

Personal 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

Disciplined approach to finding root cause by treating debugging as a scientific investigation, not a guessing game.

## Context

You are guiding systematic bug investigation. Your role is to:

- Help formulate clear, testable hypotheses about the failure
- Design minimal experiments to test each hypothesis
- Eliminate impossible causes systematically
- Narrow the problem space with each iteration
- Document findings to prevent regression

Debugging is hypothesis-driven experimentation, not random code inspection or prayer-driven programming.

## Domain Context

Based on Zeller's _Why Programs Fail_ and Robert C. Martin's discipline of debugging:

- **Reproducibility**: If you can't reproduce the bug consistently, it's a ghost. Spend time here.
- **Isolation**: What conditions trigger it? Code path, specific data, timing, environment?
- **Hypothesis**: What do you think went wrong? Must be falsifiable (testable).
- **Experiment Design**: Minimal change to test hypothesis. Change one thing at a time.
- **Iteration**: Each failed hypothesis narrows the search space. No progress = reassess assumptions.
- **Root Cause vs Symptom**: Fix the root cause, not the symptom. Symptoms can hide real problems.
- **Debugger > Print Statements**: Debuggers let you inspect state at breakpoints. Prints are for logging, not debugging.

## When to Use This Skill

- Bug is reported but you can't reproduce it yet
- Bug reproduced but root cause is unclear
Read the full skill on GitHub

Details

Skill name
systematic-debugging
Path
engineer/debugging/skills/systematic-debugging/SKILL.md
License
MIT
Repo updated
11 March 2026

FAQ

What does the Systematic Debugging skill do?

Disciplined methodology to isolate bugs through hypothesis-driven testing. Form hypotheses, test them with minimal changes, narrow scope systematically. Use when bugs are unclear or reproduce intermittently.

How do I install the Systematic Debugging skill?

Claude Code plugin: /plugin marketplace add sethdford/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 sethdford/claude-skills, which has 48 GitHub stars and 10 forks.

Related skills

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.