systematic-debugging

Guide engineers through a four-phase root-cause investigation workflow.

Updated Aug 23, 2026

Search Tags:#debugging #investigation #defense-in-depth #systematic #phases #root-cause

Ready to run

npx skills add https://github.com/ederheisler/agent-skills --skill systematic-debugging-ederheisler

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/ederheisler/agent-skills/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/ederheisler/agent-skills --skill systematic-debugging-ederheisler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Debugging provides a disciplined framework to reliably uncover root causes before proposing fixes, reducing symptom-driven patches.

Core Features & Use Cases

Phase-driven methodology for Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation.
Guards against shortcuts under time pressure and during critical incidents.
Broad applicability to bugs, test failures, and production issues with guidance on defense-in-depth.

Quick Start

To get started, read the overview and follow the four phases in order to complete a root-cause investigation.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is a systematic debugging process for finding root causes?▼

Systematic debugging is a structured methodology enforcing data gathering, reproducible steps, and explicit decision gates to reliably uncover root causes before applying fixes, reducing symptom-driven patches.

How do I debug production incidents without taking shortcuts under pressure?▼

Debug production incidents by following a four-phase workflow: root-cause investigation, pattern analysis, hypothesis testing, and implementation, which guards against shortcuts during critical incidents.

How do I investigate test failures to find the actual root cause?▼

Investigate test failures by applying a phase-driven methodology for root cause investigation, pattern analysis, hypothesis testing, and disciplined implementation to prevent quick symptom fixes.

When should I use a systematic root cause investigation instead of a quick fix?▼

Use systematic root cause investigation whenever you face bugs, test failures, or production issues to ensure robust fixes and apply defense-in-depth, avoiding unreliable symptom-driven patches.

What are the phases of systematic debugging for software engineering?▼

The phases of systematic debugging are root-cause investigation, pattern analysis, hypothesis and testing, and implementation, providing a disciplined framework to resolve software issues reliably.

Can I apply systematic debugging to both bugs and production incidents?▼

Yes, systematic debugging has broad applicability to bugs, test failures, and production issues, offering guidance on defense-in-depth and enforcing reproducible steps and decision gates.