systematic-debugging

This skill guides you through a disciplined five-phase debugging workflow designed to eliminate guesswork and prevent band-aid fixes. Start by reliably reproducing the issue, then systematically narrow down the failing component, trace the chain of causation, apply a minimal fix at the root cause, and finally verify the solution works without introducing new problems. The methodology emphasizes understanding *why* a bug occurs before attempting repairs.

Systematic Debugging teaches a five-phase methodology to reproduce, isolate, trace, fix, and verify bugs at their root cause.

AI-generated summary based on this skill's SKILL.md

★ 62 ⁮ 18 MIT updated 2026-07-18 by bobmatnyc

Install

bobmatnyc/claude-mpm-skills/systematic-debugging · repository language: Python

Manual (git clone) CLI (skillfed)

git clone https://github.com/bobmatnyc/claude-mpm-skills
cp -r claude-mpm-skills/universal/debugging/systematic-debugging ~/.claude/skills/systematic-debugging

npx skillfed install bobmatnyc/claude-mpm-skills/systematic-debugging

Frequently asked questions

AI-generated answers based on this skill's SKILL.md and metadata

What is the systematic-debugging skill's core approach?

systematic-debugging guides you through a disciplined five-phase workflow to eliminate guesswork and prevent band-aid fixes. You start by reliably reproducing the issue, then systematically narrow down the failing component, trace the chain of causation, apply a minimal fix at the root cause, and finally verify the solution works without introducing new problems. The methodology emphasizes understanding *why* a bug occurs before attempting repairs.

How do I follow a step by step debugging workflow?

systematic-debugging's workflow consists of five phases: first, reliably reproduce the bug so you can observe it consistently; second, systematically narrow down which component is failing; third, trace the chain of causation to understand how the error propagates; fourth, apply a minimal fix directly at the root cause rather than masking symptoms; and fifth, verify your fix works and doesn't introduce regressions. This structured approach prevents jumping to conclusions.

How does systematic-debugging help isolate bugs in code?

systematic-debugging teaches you to isolate bugs by first reproducing them reliably, then methodically narrowing the scope of investigation. Rather than applying random changes, you trace the error's origin by examining the chain of causation—following how data flows and functions call each other. This disciplined isolation prevents the common pitfall of shotgun debugging, where developers make multiple changes without understanding which one actually fixes the problem.

What common debugging mistakes does this skill help me avoid?

systematic-debugging helps you avoid band-aid fixes that mask symptoms without addressing root causes, shotgun debugging where you change multiple things at once, and guesswork-driven troubleshooting. By emphasizing understanding *why* a bug occurs before repairs, and by requiring verification that fixes don't introduce regressions, the skill steers you toward proper solutions that remain stable and maintainable.

How can systematic-debugging help me reproduce intermittent errors?

systematic-debugging's first phase focuses on reliably reproducing the issue—critical for intermittent bugs that are hard to trigger. The skill guides you to identify the conditions, inputs, or timing that cause the bug to appear consistently, transforming a sporadic problem into a reproducible one. Once you can trigger it reliably, the remaining phases of narrowing, tracing, fixing, and verifying become much more effective.

How does systematic-debugging verify that bug fixes work properly?

systematic-debugging includes a dedicated verification phase where you confirm your fix resolves the original issue and doesn't introduce new problems or regressions. This final phase ensures your minimal root-cause fix actually solves the problem you identified through tracing, and that the solution is stable and complete rather than a temporary workaround.

SKILL.md

rendered from the published skill — quoted content, verbatim