systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: earchibald

Guide root-cause investigation of bugs through a four-phase debugging workflow.

70|6|Updated Feb 8, 2026

Search Tags:#quality-assurance #root-cause-analysis #pattern-analysis #hypothesis-testing #systematic-debugging #bug-investigation #reproduce-errors

Ready to run

npx skills add https://github.com/earchibald/vsc-superpowers --skill systematic-debugging-earchibald

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/earchibald/vsc-superpowers/tree/main/.agents/skills/investigate
Command: npx skills add https://github.com/earchibald/vsc-superpowers --skill systematic-debugging-earchibald

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging provides a disciplined approach to identify root causes before attempting fixes, reducing wasted effort on symptom fixes.

Core Features & Use Cases

Structured Phases: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation for traceable fixes.
Evidence-Driven: Emphasizes reproducibility, data collection, and incremental changes to validate hypotheses.
Use Case: When a test fails or an intermittent bug occurs, follow the four-phase process to pinpoint root cause and verify the fix before release.

Quick Start

Follow Phase 1 steps to reproduce the issue, collect error messages, and begin root-cause investigation before any code changes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is systematic root-cause investigation for software bugs?▼

Systematic root-cause investigation is a disciplined debugging approach that identifies the underlying cause of bugs before attempting fixes. It uses a structured four-phase workflow to reduce wasted effort on treating symptoms rather than actual failures.

How do I debug intermittent production bugs and test failures?▼

Debug intermittent production bugs and test failures by following a structured workflow: reproduce the issue, collect error messages, analyze patterns, test hypotheses with incremental changes, and verify the fix before release.

Does this systematic debugging approach work for build errors and performance issues?▼

Yes, this systematic debugging approach works for build errors and performance issues. The four-phase workflow applies across diverse software projects, enforcing evidence gathering and pattern comparison to pinpoint root causes accurately.

What's the best way to stop fixing symptoms and find the root cause of errors?▼

The best way to find the root cause of errors is using evidence-driven hypothesis testing. By comparing patterns and applying minimal incremental changes to validate hypotheses, you ensure fixes target the actual failure rather than superficial symptoms.

How do I start a root-cause investigation before changing any code?▼

Start a root-cause investigation by reproducing the issue and collecting error messages. Phase 1 enforces evidence gathering and data collection to understand the failure completely before making any code changes.