systematic-debugging

Diagnose software bugs through a four-phase root cause investigation process.

69|19|Updated Jan 26, 2026

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

Ready to run

npx skills add https://github.com/alffei/skill_share --skill systematic-debugging-alffei

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a disciplined, four-phase framework for diagnosing and fixing bugs quickly and reliably, reducing time-to-resolution by preventing symptom fixes.

Core Features & Use Cases

Four-phase process (Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation) that ensures each bug is traced to its source.
Supporting techniques like root-cause tracing and defense-in-depth to prevent regressions.
Useful for any technical issue, from flaky tests to production outages.

Quick Start

Start by reading the error, reproducing it, reviewing recent changes, and then follow Phase 1 through Phase 4 to identify and fix the root cause.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

How do I find the root cause of a bug instead of just fixing symptoms?▼

To find the root cause of a bug, follow a structured four-phase process: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation. This ensures bugs are traced to their source rather than patching surface-level issues.

What is the best way to debug production incidents with deep call stacks?▼

The best way to debug production incidents with deep call stacks is using a disciplined debugging framework that traces errors to their origin. It enforces root cause investigation and adds defense-in-depth practices to prevent future regressions.

How do I systematically debug flaky tests and CI pipeline failures?▼

Systematically debug flaky tests and CI pipeline failures by reading the error, reproducing it, and reviewing recent changes. Then apply the four-phase debugging method to identify and fix the underlying root cause reliably.

Does a structured debugging process help prevent code regressions?▼

Yes, a structured debugging process prevents code regressions by incorporating defense-in-depth practices alongside root-cause tracing. This ensures fixes target the actual origin of the issue rather than merely treating symptoms.

When should I use a hypothesis-driven debugging method?▼

Use a hypothesis-driven debugging method when facing complex technical issues where deep call stacks obscure the origin. It guides you through forming and testing hypotheses to verify the root cause before implementing a fix.

What are the limitations of fixing symptoms during software debugging?▼

Fixing symptoms during software debugging limits resolution by failing to address the actual origin of the issue, which often leads to repeated failures and regressions. A structured root cause investigation is required for a permanent fix.