Systematic Debugging

Diagnose complex bugs using a four-phase root-cause debugging process.

Updated Sep 7, 2024

Search Tags:#testing #debugging #anti-patterns #root-cause #phase-based #reproducible-workflow

Ready to run

npx skills add https://github.com/Asylcreek/home-manager --skill systematic-debugging-asylcreek

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Systematic Debugging
Source: https://github.com/Asylcreek/home-manager/tree/main/dots/agents/skills/systematic-debugging
Command: npx skills add https://github.com/Asylcreek/home-manager --skill systematic-debugging-asylcreek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Debugging provides a disciplined, four-phase approach to diagnosing root causes rather than applying symptom fixes under pressure.

Core Features & Use Cases

Phase-based workflow: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation with strict gates.
Built-in safeguards: do not proceed to fixes before Phase 1; anti-patterns; testing scenarios.
Real-world guidance: examples for flaky tests, time pressure, and architectural questions.
Reproducible methodology across bug types: production bugs, tests, integrations.

Quick Start

Follow the four phases in order: begin with Phase 1 root-cause investigation, then proceed to Pattern Analysis, Hypothesis and Testing, and Implementation with verification.

Frequently Asked Questions about Systematic Debugging

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

FAQPage Schema

How do I debug complex software failures instead of just fixing symptoms?▼

Root-cause debugging enforces a four-phase workflow—investigation, pattern analysis, hypothesis testing, and implementation—mandating Phase 1 completion before applying any fixes to prevent superficial symptom patching.

What is the best way to debug flaky tests under time pressure?▼

Debug flaky tests under time pressure by applying a reproducible, phase-based methodology with built-in anti-patterns and validation-oriented testing scenarios that guide you from root cause investigation to verified implementation.

How do I diagnose production outages systematically without skipping steps?▼

Diagnose production outages systematically by following strict phase gates—root cause investigation, pattern analysis, hypothesis and testing, then implementation—preventing premature fixes before root cause identification.

Can I use a phase-based debugging workflow for multi-layered system failures?▼

A phase-based debugging workflow applies to multi-layered failures across production bugs, integrations, and flaky tests. The methodology remains reproducible across bug types while enforcing hypothesis validation before implementation.

Why does my debugging process keep producing recurring bugs?▼

Your debugging process likely produces recurring bugs because symptom fixes are applied without root-cause investigation. Enforcing mandatory Phase 1 before fixes and using validation-oriented testing prevents superficial patches that cause regression.