Verified:GitHub

systematic-debugging

Guide root-cause debugging through four phases with decision gates.

Updated Jan 28, 2026

Search Tags:#defense-in-depth #quality-assurance #root-cause #phase-based #systematic-debugging #root-cause-tracing #debugging-process

Ready to run

npx skills add https://github.com/kckylechen1/ai-agent-toolkit --skill systematic-debugging-kckylechen1

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, phase-based approach to debugging, ensuring root-cause analysis before any fixes to prevent symptom-driven work.

Core Features & Use Cases

Phase-driven workflow with four phases: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation.
Defense-in-depth mindset that adds layered checks to catch edge cases and bypass shortcuts.
Applicable to bugs, test failures, performance issues, and integration problems across projects and teams.

Quick Start

Load the skill and follow Phase 1 (Root Cause Investigation) before attempting any fixes. Use the other phases as guidance when the root cause remains unclear.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

How do I fix recurring software bugs instead of just patching symptoms?▼

To fix recurring software bugs instead of patching symptoms, use a phase-based root-cause investigation workflow that enforces analysis before implementation. This approach adds defense-in-depth validation to catch edge cases and ensure the actual flaw is resolved.

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

The best way to debug flaky tests and production outages is applying a systematic debugging process with explicit decision gates. This structured workflow ensures you stop and re-evaluate hypotheses when root causes remain unclear across complex integration issues.

How do you carry out root-cause tracing for complex integration issues?▼

Root-cause tracing for complex integration issues requires a four-phase process: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation. You must complete the initial investigation phase before attempting any code fixes.

When should I stop and re-evaluate during the debugging process?▼

You should stop and re-evaluate during the debugging process when reaching explicit decision gates and the root cause remains unclear. This phase-based methodology prevents symptom-focused work and ensures rigorous analysis before proceeding to implementation.

Does a systematic debugging workflow work for small codebases and large teams?▼

Yes, a systematic debugging workflow applies to software engineering challenges across codebases of varying sizes. It provides a structured phase-based process and defense-in-depth validation suitable for both small projects and large teams.

Why does symptom-focused debugging fail to permanently fix software issues?▼

Symptom-focused debugging fails because it bypasses root-cause investigation and applies immediate fixes without pattern analysis. A rigorous phase-based workflow with layered checks is required to catch edge cases and prevent recurring failures.