systematic-debugging

Identify root causes of bugs through a four-phase debugging workflow.

Updated Aug 27, 2026

Search Tags:#debugging #anti-patterns #validation #defense-in-depth #systematic #phases #root-cause

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/ctrlShiftBryan/dotfiles/tree/main/claude/.claude/skills/systematic-debugging
Command: npx skills add https://github.com/ctrlShiftBryan/dotfiles --skill systematic-debugging-ctrlshiftbryan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps identify the root cause of bugs and failures before proposing fixes.

Core Features & Use Cases

Four-phase systematic debugging workflow (Root Cause Investigation → Pattern Analysis → Hypothesis & Testing → Implementation)
Enforces strict phase order with explicit prerequisites
Anti-patterns and defense-in-depth guidance to prevent shortcut fixes
Practical guidance for real-world debugging scenarios

Quick Start

Follow Phase 1 through Phase 4 in order to uncover root causes and implement robust fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is systematic debugging and when do I need it?▼

Systematic debugging is a structured four-phase workflow to identify root causes before applying fixes. You need it for complex systems, flaky tests, or debugging under time pressure across development, staging, and production environments.

How do I find the root cause of a bug before fixing it?▼

To find the root cause, follow the four phases in order: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation. Each phase has explicit prerequisites that must be met before advancing to the next.

What's the best way to stop applying shortcut fixes to recurring bugs?▼

The best way to stop shortcut fixes is to enforce anti-patterns and defense-in-depth practices during debugging. This approach mandates strict phase ordering and hypothesis testing to ensure robust root-cause resolution.

Can I use a systematic debugging workflow for flaky tests in production?▼

Yes, this systematic debugging workflow applies to flaky tests and production failures. It provides practical guidance for real-world scenarios, ensuring you identify root causes even under time pressure in complex systems.

Why does my debugging process keep missing the actual root cause?▼

Your debugging process misses the root cause when skipping prerequisites between phases. Enforcing a strict four-phase workflow with pattern analysis and hypothesis testing prevents superficial fixes and targets the source.