systematic-debugging

Guide engineers through a four-phase debugging process to identify root causes.

Updated Jan 22, 2026

Search Tags:#testing #debugging #quality #root-cause #bug-fix #phased-workflow

Ready to run

npx skills add https://github.com/blake-goodwyn/sloppy-pancakes --skill systematic-debugging-blake-goodwyn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/blake-goodwyn/sloppy-pancakes/tree/main/.claude/skills/systematic-debugging
Command: npx skills add https://github.com/blake-goodwyn/sloppy-pancakes --skill systematic-debugging-blake-goodwyn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined, 4-phase approach to debugging that identifies root causes rather than guessing at fixes.

Core Features & Use Cases

Phase-based workflow: Reproduce, Isolate, Root Cause, and Fix & Verify to structure debugging efforts.
Documentation and evidence: Guides collecting reproducible steps, logs, and test evidence to prove issues and fixes.
Use Case: When a bug is persistent, flaky, or hard to reproduce, this Skill helps teams systematically locate and validate the underlying cause.

Quick Start

Call the systematic-debugging skill to guide your team through the four phases on a failing feature and produce a reproducible plan for remediation.

Frequently Asked Questions about systematic-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I debug a persistent bug using a systematic root-cause workflow?▼

Systematic debugging resolves a persistent bug by enforcing a four-phase workflow: Reproduce, Isolate, Root Cause, and Fix & Verify. This disciplined process collects logs and test evidence to validate the underlying cause rather than guessing at fixes.

What is the best way to find the root cause of flaky tests across a codebase?▼

Finding the root cause of flaky tests requires isolating the failure through a phased debugging workflow. By reproducing the issue and collecting reproducible steps and logs, teams can systematically locate and validate the underlying cause across codebases.

Can I use a phased debugging approach for hard-to-reproduce failures?▼

A phased debugging approach works effectively for hard-to-reproduce failures by structuring the investigation into Reproduce, Isolate, Root Cause, and Fix & Verify. It guides engineers to gather documentation and evidence to prove the issue and remediate it.

Does systematic debugging require specific testing frameworks to isolate bugs?▼

Systematic debugging does not require specific testing frameworks to isolate bugs. It is a dependency-free workflow that guides engineers through collecting test evidence and reproducible steps to validate improvements across any codebase.

Why should I use a root-cause debugging workflow instead of guessing fixes?▼

A root-cause debugging workflow prevents recurring issues by enforcing evidence collection and isolation before applying fixes. Unlike guessing, this disciplined four-phase process ensures you validate the underlying cause with documentation and tests.

What are the limitations of using a basic debugging workflow for complex codebases?▼

The limitation of this basic debugging workflow is that it provides a structured process rather than automated analysis. Engineers must manually execute the four phases—Reproduce, Isolate, Root Cause, Fix & Verify—to collect evidence and validate improvements.