Systematic Debugging

Four-phase debugging methodology — investigate, analyze patterns, test hypotheses, and implement fixes with full root-cause traceability.

Features

• Root Cause Analysis — Traces bugs backward through the call stack to find the original trigger
• Pattern Recognition — Identifies recurring error patterns and suggests systemic fixes
• Hypothesis Testing — Generates and validates multiple bug hypotheses before committing to a fix
• Regression Prevention — Creates targeted regression tests for every bug fix
• Debug Log Analysis — Parses stack traces and log files to pinpoint failure origins

Quick Start

claude skill install systematic-debugging

Usage

# Debug a specific error message
/systematic-debugging "TypeError: Cannot read property 'id' of undefined"

# Analyze a failing test
/systematic-debugging --test src/auth.test.ts

How It Works

Follows a structured four-phase approach: (1) Investigate by gathering error context and reproducing the issue, (2) Analyze patterns across related code paths, (3) Test hypotheses with minimal targeted changes, (4) Implement the fix with regression tests. Each phase produces documented evidence for traceability.

Compatibility

Works with Claude Code, Codex, Gemini CLI, Cursor, Windsurf, and Aider.