systematic-debugging

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

Updated Jan 20, 2026

Search Tags:#debugging #defense-in-depth #phases #hypothesis #root-cause #evidence-based

Ready to run

npx skills add https://github.com/hitsumabushi334/KGpaper --skill systematic-debugging-hitsumabushi334

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/hitsumabushi334/KGpaper/tree/main/.agent/Skills/systematic-debugging
Command: npx skills add https://github.com/hitsumabushi334/KGpaper --skill systematic-debugging-hitsumabushi334

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers avoid symptom-driven fixes by enforcing a disciplined root-cause approach to debugging.

Core Features & Use Cases

Four-Phase Method: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation.
Anti-pattern Awareness: Stops shortcuts and promotes data-driven decisions with explicit failure modes and defenses.
Real-World Scenarios: Useful for production outages, flaky tests, and complex integration bugs.

Quick Start

Load the skill and follow Phase 1: Root Cause Investigation before proposing any fixes, then validate at each phase with concrete evidence.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

How do I identify the root cause of a bug instead of just fixing symptoms?▼

Root-cause debugging requires a four-phase process: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation. This structured approach enforces evidence-based decisions to prevent symptom-driven fixes.

What is the best way to debug production outages and flaky tests systematically?▼

Debug production outages and flaky tests by applying a structured four-phase method. It guides you through root cause investigation, pattern analysis, hypothesis testing, and implementation with concrete evidence validation.

How do I test a debugging hypothesis before proposing code fixes?▼

Test a debugging hypothesis during the third phase of systematic debugging. This phase requires gathering concrete evidence and data-driven validation to confirm the root cause before moving to the implementation phase.

When do I need a defense-in-depth approach for resolving complex integration bugs?▼

A defense-in-depth approach is needed for complex integration bugs when symptom-driven fixes fail. It enforces explicit failure mode awareness and robust validation across the four phases to ensure resilient resolutions.

Does systematic debugging require any specific testing frameworks or dependencies?▼

Systematic debugging requires no specific testing frameworks or dependencies. It is a methodology that applies across production outages, flaky tests, and integration issues by enforcing evidence-based investigation regardless of the tech stack.