systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: duyseu

Enforce root-cause investigations across a four-phase debugging framework.

1|Updated Aug 17, 2025

Search Tags:#testing #debugging #anti-patterns #defense-in-depth #phases #root-cause #root-cause-tracing

Ready to run

npx skills add https://github.com/DuySeu/StockMind --skill systematic-debugging-duyseu

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Random fixes waste time and create new bugs. Quick patches mask underlying issues. Core principle: ALWAYS find root cause before attempting fixes. Violating the letter of this process is violating the spirit of debugging.

Core Features & Use Cases

The skill provides a four-phase framework (Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation) with explicit rules, checks, and anti-patterns to resist time-pressure shortcuts; it also includes defense-in-depth concepts and practical testing guidance that ensure fixes address the real cause and prevent regressions.

Quick Start

Follow Phase 1: read the overview and complete Phase 1 before attempting any fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is systematic debugging and how does it prevent symptom-based fixes?▼

Systematic debugging is a four-phase framework enforcing root-cause investigations to prevent symptom-based patches. It traces data flow, analyzes patterns, forms hypotheses, and implements robust fixes to ensure underlying issues are resolved rather than masked.

How do I find the root cause of a bug before attempting a fix?▼

To find the root cause of a bug, follow the four-phase framework: start with Root Cause Investigation, move to Pattern Analysis, then Hypothesis & Testing, and finally Implementation. You must complete Phase 1 before attempting any fixes to resist time-pressure shortcuts.

Why do quick patches and random fixes create new bugs during debugging?▼

Quick patches and random fixes create new bugs because they mask underlying issues without addressing the actual fault. Systematic debugging prevents this by enforcing root-cause tracing and defense-in-depth validations, ensuring fixes target the real problem and prevent regressions.

Can I use a structured debugging framework for production incidents and test failures?▼

Yes, you can use this structured debugging framework for production incidents and test failures. It applies to bug investigations by guiding practitioners to trace data flow, analyze patterns, and implement robust fixes across its four-phase process.

What are the limitations of symptom-based debugging when handling production incidents?▼

Symptom-based debugging wastes time and creates regressions under time pressure. The limitation is that without a structured four-phase framework enforcing root-cause tracing, fixes remain superficial and lack the defense-in-depth validations needed to prevent recurring incidents.

What is the best way to structure a root-cause investigation for complex software bugs?▼

The best way to structure a root-cause investigation is using a four-phase framework: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation. This approach resists shortcuts and incorporates defense-in-depth concepts to prevent future regressions.