systematic-debugging

Find root causes of bugs through a four-phase evidence-based process.

Updated Jan 12, 2026

Search Tags:#testing #debugging #defense-in-depth #root-cause #phase-based #root-cause-tracing

Ready to run

npx skills add https://github.com/Suara17/guanlan-sina --skill systematic-debugging-suara17

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/Suara17/guanlan-sina/tree/main/.opencode/skills/systematic-debugging
Command: npx skills add https://github.com/Suara17/guanlan-sina --skill systematic-debugging-suara17

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables structured debugging to identify root causes of bugs rather than patching symptoms, reducing wasted time and rework.

Core Features & Use Cases

Four-phase workflow: Phase 1 root-cause investigation, Phase 2 pattern analysis, Phase 3 hypothesis testing, Phase 4 implementation with validation.
Guardrails against shortcuts: Enforces explicit data gathering, evidence, and checks before fixes.
Use Case: When a bug appears in production or during testing, apply the method to trace data flow and verify root cause.

Quick Start

Load the skill and follow Phase 1, then Phase 2, Phase 3, and Phase 4 to resolve issues with confirmed root causes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is root-cause debugging and how does it prevent symptom-focused fixes?▼

Root-cause debugging is a structured method to identify the actual source of software defects rather than patching symptoms. It enforces explicit evidence gathering and data flow tracing before applying any fixes, which reduces wasted time and rework.

How do I find the root cause of a bug using a phase-based process?▼

To find the root cause of a bug, follow a four-phase process: investigate the root cause, analyze patterns, test hypotheses, and implement with validation. This enforces evidence checks at each step to ensure confirmed root causes before fixes.

When should I use a systematic debugging workflow for software defects?▼

Use systematic debugging when a bug appears in production, staging, or during testing. It is designed for unexpected behavior across these environments, enforcing data gathering and hypothesis testing to verify the root cause before applying any code changes.

Can I use this structured debugging method for test failures in production?▼

Yes, this structured debugging method applies directly to test failures and unexpected behavior in production. It enforces a phase-based workflow that relies on gathering evidence and tracing data flow to resolve issues with confirmed root causes.

What is the best way to trace unexpected behavior without taking shortcuts?▼

The best way to trace unexpected behavior is using guardrails that enforce explicit data gathering and evidence checks. A four-phase workflow prevents symptom-focused fixes by requiring pattern analysis and hypothesis testing before final implementation.

Why does patching symptoms fail to resolve recurring software defects?▼

Patching symptoms fails because it skips root-cause investigation and pattern analysis. Without a phase-based debugging process that enforces evidence gathering and hypothesis testing, the underlying defect remains unresolved, leading to wasted time and rework.