systematic-debugging

Enforce a four-phase root-cause debugging process for code and tests.

14|1|Updated Dec 29, 2011

Search Tags:#debugging #validation #trace #hypothesis #root-cause #phase-based

Ready to run

npx skills add https://github.com/doitian/dotfiles-public --skill systematic-debugging-doitian

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/doitian/dotfiles-public/tree/main/ai/workflows/superpowers/skills/systematic-debugging
Command: npx skills add https://github.com/doitian/dotfiles-public --skill systematic-debugging-doitian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging provides a disciplined, phase-driven approach to identifying root causes before proposing fixes, reducing time wasted on symptom fixes.

Core Features & Use Cases

Phase-based workflow covering Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation
Anti-patterns, defense-in-depth, and structured validation to prevent regression
Guidance for tracing data flow, gathering evidence, and writing robust fixes
Real-world impact demonstrated by systematic debugging practice and tests

Quick Start

Read and apply the four phases in sequence to uncover the root cause before implementing a 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 fixes?▼

Root-cause debugging enforces a phase-driven process to identify the actual origin of a bug before proposing fixes. It eliminates wasted time on symptom fixes by demanding evidence gathering and trace-based analysis across code, tests, and production scenarios.

How do I systematically debug a bug in production?▼

Systematic debugging requires a four-phase process: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation. You trace data flow, gather evidence, validate hypotheses, and implement a structured fix to resolve production bugs.

Does systematic debugging work for fixing failing tests and code regressions?▼

Yes, systematic debugging applies to code, tests, and production scenarios. It uses structured validation, anti-patterns, and defense-in-depth techniques during the Implementation phase to ensure robust fixes and prevent future regressions.

What's the best way to trace data flow to find a bug's root cause?▼

The best way is applying the Root Cause Investigation and Pattern Analysis phases. You trace data flow, gather concrete evidence, and analyze patterns to formulate a validated hypothesis, ensuring you address the actual fault rather than surface symptoms.

Why should I use a phase-based debugging approach instead of patching symptoms?▼

A phase-based debugging approach stops you from wasting time on symptom fixes. By enforcing multi-phase validation from investigation to implementation, it ensures you resolve the underlying root cause and build defense-in-depth against regressions.

When should I not use hypothesis-driven debugging for code validation?▼

You should not skip hypothesis-driven debugging when facing complex code, tests, or production issues requiring trace-based analysis. Without multi-phase validation, you risk implementing symptom fixes that cause future regressions and instability.