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
Decision gist · record as of 2026-07-18
Systematic Debugging teaches a five-phase methodology to reproduce, isolate, trace, fix, and verify bugs at their root cause. 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.
Use it when
- systematic-debugging's workflow consists of five phases: first, reliably reproduce the bug so you can observe it consistently.
- systematic-debugging teaches you to isolate bugs by first reproducing them reliably, then methodically narrowing the scope of investigation.
Verify before relying
Read SKILL.md below before installing (6 files). Open directory: indexed for reading, not audited.
Install
bobmatnyc/claude-mpm-skills/systematic-debugging · repository language: Python
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
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.
Systematic Debugging
When to Use
- A bug, error, exception, or crash needs investigation
- Something is "not working" and the cause is unclear
-
A test is failing and the reason isn't obvious
(truncated - see the full file via the links below)
File tree — 6 files
universal/debugging/systematic-debugging/SKILL.md
universal/debugging/systematic-debugging/metadata.json
universal/debugging/systematic-debugging/references/anti-patterns.md
universal/debugging/systematic-debugging/references/examples.md
universal/debugging/systematic-debugging/references/troubleshooting.md
universal/debugging/systematic-debugging/references/workflow.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Learn a structured debugging methodology to find and fix bugs systematically”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
A disciplined, evidence-based debugging framework that walks you through reproducing issues reliably, narrowing scope to the failing component, understanding root causes through the scientific method, and implementing minimal fixes with regression tests. Eliminates guesswork and ensures you address the actual problem, not just symptoms.
Systematic Debugging guides you through a proven 4-phase process: reproduce the issue reliably, isolate its source, analyze root causes using techniques like the 5 Whys, and verify your fix works without introducing new problems. This skill prevents random troubleshooting and ensures you understand what's broken before attempting repairs.
Systematic Debugging enforces a disciplined four-phase process: investigate root cause, analyze patterns, form and test hypotheses, then implement fixes. It stops you from guessing at solutions and catching yourself in cycles of failed patches that mask underlying problems.
This skill enforces a disciplined debugging methodology that prioritizes root cause discovery over quick patches. Work through four phases—investigation, pattern analysis, hypothesis testing, and implementation—completing each before advancing. The framework prevents the trap of symptom-fixing by requiring evidence gathering across component boundaries and data flow tracing before any fix attempt.
Systematic Debugging teaches a disciplined four-phase process for tackling any technical issue—from test failures to production bugs. By enforcing root cause investigation before attempting fixes, it eliminates guesswork and the cycle of symptom-patching that creates new problems. The framework emphasizes evidence gathering, pattern analysis, hypothesis testing, and architectural questioning when multiple fixes fail.
Systematic Debugging enforces a disciplined four-phase approach to troubleshooting: start with root cause investigation, then research external context, analyze patterns, and test hypotheses before implementing any fix. The skill prevents the common trap of patching symptoms, ensuring you understand what actually broke and why.