systematic-debugging

Apply a four-phase debugging process to identify root causes before fixing.

Updated Apr 16, 2014

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

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Debugging provides a disciplined, four-phase framework to diagnose bugs, avoid symptom fixes, and consistently uncover root causes.

Core Features & Use Cases

Four-phase methodology: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation with explicit guardrails.
Anti-shortcut rules: STOP and re-analyze if needed; never fix symptoms first.
Defense-in-depth guidance: Encourages multiple validation layers and stack-trace instrumentation to prevent regressive fixes.
Use Case: Teams under time pressure use it to reduce debugging time while improving fix quality.

Quick Start

Follow Phase 1 checklist before attempting any fix.

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 the root cause of software bugs?▼

A systematic debugging process enforces a disciplined four-phase methodology—Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation—to uncover the true origin of software bugs before applying any fixes.

How do I debug a production incident without just fixing the symptoms?▼

To debug a production incident without fixing symptoms, follow explicit guardrails that force root-cause investigation first. You must gather concrete evidence and validate hypotheses during structured phases before attempting any code implementation.

What steps should I follow to investigate root cause before fixing a technical issue?▼

Investigate root cause by completing Phase 1 checklist first, which involves gathering concrete evidence. Progress through Pattern Analysis and Hypothesis & Testing phases, ensuring you never bypass root-cause validation to implement a quick symptom fix.

Can I use systematic debugging for unit test failures under time pressure?▼

Yes, systematic debugging applies to any technical issue from unit test failures to production incidents, especially under time pressure. It enforces anti-shortcut rules and defense-in-depth validation to improve fix quality while reducing overall debugging time.

Why do my bug fixes cause regressions in other parts of the system?▼

Bug fixes cause regressions when they target symptoms instead of the root cause. Systematic debugging applies defense-in-depth guidance with multiple validation layers and stack-trace instrumentation to prevent regressive fixes from occurring.

What is the best way to stop developers from applying quick fixes during incident response?▼

The best way to stop quick fixes is enforcing an anti-shortcut rule that requires developers to STOP and re-analyze if they attempt a symptom-focused fix. The four-phase methodology explicitly blocks implementation until root cause is confirmed.