systematic-debugging

Systematizes software debugging via Investigation, Analysis, Hypothesis, Implementation phases.

Updated May 9, 2026

Search Tags:#debugging #root cause #troubleshooting #systematic #error analysis #software testing

Ready to run

npx skills add https://github.com/duongbui234/ag-skills-pro --skill systematic-debugging-duongbui234

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/duongbui234/ag-skills-pro/tree/main/template/.agent/skills/systematic-debugging
Command: npx skills add https://github.com/duongbui234/ag-skills-pro --skill systematic-debugging-duongbui234

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill prevents the common trap of applying quick, superficial patches that mask underlying issues and create new bugs, ensuring that technical problems are resolved permanently.

Core Features & Use Cases

Root Cause Mandate: Enforces a strict four-phase process (Investigation, Pattern Analysis, Hypothesis, Implementation) to ensure the source of the error is addressed rather than the symptom.
Defense-in-Depth: Provides techniques for adding validation at multiple layers of the stack to make bugs structurally impossible.
Use Case: When a production API fails intermittently, use this skill to trace the data flow, identify the specific failing component, and implement a robust fix that includes automated testing and environment guards.

Quick Start

Invoke the systematic debugging skill to begin a structured investigation of the current test failure or production bug.

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 flaky test instead of just patching the symptom?▼

To find the root cause of a flaky test, enforce a systematic four-phase debugging process: Investigation, Pattern Analysis, Hypothesis, and Implementation. This scientific approach traces data flow to resolve defects permanently.

What is the best way to debug intermittent production API failures?▼

The best way to debug intermittent production API failures is applying systematic error analysis. Trace the data flow to identify the specific failing component, then implement a robust fix using multi-layer validation strategies.

How does systematic debugging prevent superficial patches that create new bugs?▼

Systematic debugging prevents superficial patches by mandating scientific hypothesis testing and multi-layer validation. This defense-in-depth approach ensures architectural integrity by making bugs structurally impossible to reappear.

Can I use a root cause analysis framework for complex technical issues beyond software testing?▼

Yes, you can use a root cause analysis framework for complex technical issues and production failures. The systematic debugging process applies scientific hypothesis testing to resolve diverse software defects comprehensively.

What are the four phases of systematic troubleshooting for software defects?▼

The four phases of systematic troubleshooting are Investigation, Pattern Analysis, Hypothesis, and Implementation. This structured process enforces root cause identification to prevent symptom-based patching.

When should I use a systematic error analysis process instead of quick fixes?▼

Use systematic error analysis instead of quick fixes when facing complex technical issues, flaky tests, or production failures. It prevents the common trap of applying superficial patches that mask underlying issues and create new bugs.