systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: miles990

Guide engineers through a four-phase root-cause debugging process.

Updated Jan 7, 2026

Search Tags:#debugging #defense-in-depth #systematic #traceability #phases #root-cause

Ready to run

npx skills add https://github.com/miles990/claude-starter-kit --skill systematic-debugging-miles990

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Systematic debugging helps engineers identify and resolve root causes before applying fixes, reducing unnecessary changes and flaky outcomes.

Core Features & Use Cases

Four-Phase Process: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation with validation.
Defense-in-Depth: Validation at multiple layers to prevent regression and ensure robust fixes.
Practical guidance: Works for bugs, test failures, production incidents, and unexpected behavior.

Quick Start

Read the error messages and reproduce the issue consistently.
Identify and analyze the failing area, then form a testable hypothesis.
Implement a fix only after confirming root cause, and verify with tests.

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 should I use it for root-cause investigation?▼

Systematic debugging is a structured method to identify and resolve root causes before applying fixes. Use it for bugs, test failures, production incidents, or unexpected behavior to reduce unnecessary changes and flaky outcomes.

How do I fix a bug systematically using root-cause analysis and hypothesis testing?▼

To fix a bug systematically, follow a four-phase process: complete root-cause investigation, pattern analysis, hypothesis testing, and implementation. You must complete each phase in order before applying fixes to ensure robust resolution.

Does systematic debugging work for production incidents and test failures?▼

Yes, systematic debugging works for production incidents and test failures. It guides engineers through root-cause investigation and pattern analysis, ensuring you confirm the root cause before implementing and validating any fixes.

What is the best way to stop guessing and find the root cause of unexpected behavior?▼

The best way to stop guessing is to reproduce the issue consistently, analyze the failing area, and form a testable hypothesis. This root-cause debugging approach beats guesswork by validating hypotheses before implementation.

How does defense-in-depth prevent regression when implementing a bug fix?▼

Defense-in-depth prevents regression by applying validation at multiple layers during the implementation phase. This systematic debugging technique ensures robust fixes and prevents unexpected behavior from reoccurring after the root cause is resolved.

Why should I not apply a fix before confirming the root cause of a failing test?▼

Applying a fix before confirming the root cause leads to unnecessary changes and flaky outcomes. Systematic debugging requires completing hypothesis testing first, ensuring the implementation phase addresses the actual failure, not just symptoms.