systematic-debugging

Identify root causes of bugs through a four-phase debugging workflow.

3|Updated Dec 22, 2025

Search Tags:#debugging #anti-patterns #defense-in-depth #root-cause #phase-based #systematic-debugging

Ready to run

npx skills add https://github.com/JoaquinCampo/codex-skills --skill systematic-debugging-joaquincampo

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a disciplined, phase-driven approach to debugging that forces root-cause investigation before fixes, reducing time wasted on symptom-only patches.

Core Features & Use Cases

Four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation, with explicit gating to prevent skipping phases.
Defensive practices: Anti-patterns, cognitive guards, and explicit validation to resist time pressure for reliable outcomes.
Real-world applicability: Effective for production outages, flaky tests, and complex failures, ensuring consistent outcomes.

Quick Start

Read the skill description and internalize the four phases.
Always complete Phase 1 before proposing fixes.
Use Phase 4 validation and defense-in-depth steps to verify the fix.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is root-cause debugging and how does it prevent symptom-only patches?▼

Root-cause debugging identifies the actual origins of bugs and failures instead of treating superficial symptoms. It enforces a four-phase workflow—investigation, pattern analysis, hypothesis testing, and implementation—to ensure underlying issues are fully resolved before fixes are applied.

How do I debug production incidents without falling back on quick fixes?▼

Debug production incidents by applying a phase-based workflow that gates fixes until root cause investigation is complete. This structured approach uses cognitive guards and anti-patterns to resist time pressure, ensuring you validate hypotheses before implementing changes.

What's the best way to find the root cause of flaky tests and complex failures?▼

The best way to find root causes of flaky tests is through systematic pattern analysis and hypothesis testing. By investigating failure patterns and validating explicit hypotheses before implementation, you isolate the true origin of the inconsistency rather than patching symptoms.

Does this systematic debugging approach work for any technical issue or only software bugs?▼

Systematic debugging applies to any technical issue, including production outages, flaky tests, and complex software failures. The four-phase workflow is domain-agnostic, enforcing root cause investigation and explicit validation regardless of the specific failure type.

When should I avoid phase-based debugging workflows during an active outage?▼

You should not avoid phase-based debugging even during active outages. The workflow is specifically designed for time-pressure scenarios, using anti-patterns and defense-in-depth validation to prevent the rushed quick fixes that often lead to recurring incidents.

How do I validate my fix after identifying a bug's root cause?▼

Validate your fix during the implementation phase by applying explicit validation and defense-in-depth steps. This ensures the root cause is fully addressed and documents the resolution to maintain consistent, reliable outcomes across the system.