systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: huanlongAI

Trace root causes through a four-phase debugging workflow.

Updated Aug 27, 2026

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

Ready to run

npx skills add https://github.com/huanlongAI/tzh-Harness --skill systematic-debugging-huanlongai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/huanlongAI/tzh-Harness/tree/main/cowork-skills/systematic-debugging
Command: npx skills add https://github.com/huanlongAI/tzh-Harness --skill systematic-debugging-huanlongai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Debugging provides a disciplined approach to diagnosing bugs, preventing rush fixes, and improving repair quality by guiding you to identify the root cause before patching.

Core Features & Use Cases

Four-phase process (Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation) with gated checks and evidence gathering.
Defense-in-depth and stack-trace techniques to locate origin across components and ensure robust fixes.
Real-world guidelines for handling environmental factors, flaky tests, and escalation.

Quick Start

Start by identifying the current bug symptom, then follow Phase 1 (Root Cause Investigation) to reproduce, gather evidence, and trace data flow before proposing any fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

How do I find the root cause of a bug instead of just patching symptoms?▼

To find the root cause of a bug, trace data flow and gather evidence across components before proposing fixes, ensuring you address the origin rather than merely patching symptoms. This systematic debugging approach enforces disciplined hypotheses and evidence gathering.

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

The best way to debug flaky tests and production bugs is using a repeatable four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation, applying defense-in-depth techniques to locate the issue origin across components.

How do I implement a systematic debugging workflow for integration problems?▼

Implement a systematic debugging workflow for integration problems by following four gated phases that enforce evidence gathering, disciplined hypotheses, and minimal incremental changes to ensure robust and maintainable fixes.

When should I apply defense-in-depth techniques during bug tracing?▼

Apply defense-in-depth techniques during bug tracing when you need to locate the origin of issues across multiple components and ensure your fixes are robust against related failures, using stack-trace analysis to validate the repair.

Can I use systematic debugging for performance issues and test failures?▼

Yes, you can use systematic debugging for performance issues and test failures. The approach applies a repeatable four-phase workflow with gated checks to reproduce the issue, analyze patterns, and implement robust fixes.

Why does patching symptoms fail to fix recurring software bugs?▼

Patching symptoms fails to fix recurring software bugs because it skips root cause investigation and evidence gathering. Without tracing data flow and analyzing patterns, the underlying issue remains unresolved, leading to repeated failures.