systematic-debugging

Enforce root-cause investigation before applying fixes in a four-phase debugging workflow.

15|2|Updated Jun 21, 2026

Search Tags:#validation #defense-in-depth #data-flow #phase-based #systematic-debugging #root-cause-tracing

Ready to run

npx skills add https://github.com/Liuchun-oss/codelf-agent --skill systematic-debugging-liuchun-oss

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/Liuchun-oss/codelf-agent/tree/main/resources/skills/systematic-debugging
Command: npx skills add https://github.com/Liuchun-oss/codelf-agent --skill systematic-debugging-liuchun-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Random debugging wastes time and creates unnecessary fixes; this skill enforces a disciplined, four-phase approach to uncover root causes before proposing changes.

Core Features & Use Cases

Four-Phase Process: Phase 1 Root Cause Investigation, Phase 2 Pattern Analysis, Phase 3 Hypothesis and Testing, Phase 4 Implementation.
Defensive Practices: anti-symptom fixes, data-flow tracing, and defense-in-depth to prevent regressions.
Use Cases: debugging production issues, flaky tests, and complex systems where timing or data flow causes failures.

Quick Start

Follow the four-phased root-cause debugging workflow to identify the true trigger before implementing fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is the best way to trace root causes before fixing production bugs?▼

Systematic debugging enforces root-cause tracing to uncover the true trigger of production bugs before proposing any code changes. This approach prevents random debugging and eliminates unnecessary symptom fixes by applying a deterministic four-phase workflow.

How do I debug flaky tests and complex data-flow failures systematically?▼

Debugging flaky tests requires data-flow tracing and pattern analysis to identify hidden timing or data dependencies. You apply a four-phase workflow to investigate the root cause, form hypotheses, and verify fixes with reproducible checks.

Why does applying quick fixes to unexpected behavior lead to code regressions?▼

Applying quick fixes to unexpected behavior often masks the underlying root cause and introduces code regressions. A defense-in-depth approach with post-fix verification ensures the true trigger is eliminated and prevents future failures.

What are the four phases of a deterministic root-cause debugging workflow?▼

The four phases are Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation. This workflow guides engineers from initial investigation through data-flow tracing to applying verified fixes.

How do I stop treating symptoms and start eliminating bugs in existing codebases?▼

To stop treating symptoms and eliminate bugs, enforce anti-symptom fixes by tracing data-flow back to the root cause. Implement defense-in-depth practices and reproducible checks to ensure fixes target the actual failure trigger.

When should I use a phase-based debugging approach instead of ad-hoc troubleshooting?▼

Use a phase-based debugging approach for complex systems, production issues, and flaky tests where timing or data flow causes failures. It provides robust debugging with multiple defense layers that ad-hoc troubleshooting lacks.