systematic-debugging

Enforce root-cause analysis before fixes across four debugging phases.

1|Updated Apr 17, 2026

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

Ready to run

npx skills add https://github.com/ccakmak60/agentforge --skill systematic-debugging-ccakmak60

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/ccakmak60/agentforge/tree/main/.trae/skills/systematic-debugging
Command: npx skills add https://github.com/ccakmak60/agentforge --skill systematic-debugging-ccakmak60

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging helps engineers uncover root causes of bugs and failures before proposing fixes, reducing wasted time on symptom patching.

Core Features & Use Cases

Four-phase framework (Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation) to guide debugging.
Evidence-driven: require reproducible steps, data gathering, and traceability across components.
Defense-in-depth mindset: encourage multi-layer validations and progressive hardening to prevent regressions.
Use Cases: production incidents, flaky tests, complex integrations, and performance anomalies.
Real-world impact: reduces time to resolution and prevents symptom-driven fixes.

Quick Start

Load the systematic-debugging skill and begin with Phase 1: Root Cause Investigation before proposing 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 when do I need it for software incidents?▼

Systematic debugging is a methodology to uncover root causes of failures before fixing them. You need it during production incidents, flaky tests, or complex integrations to stop patching symptoms and reduce time to resolution.

How do I debug software using a root cause analysis framework?▼

To debug software systematically, follow four phases: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation. Gather reproducible evidence and trace across components before proposing any fixes to ensure true root cause resolution.

How to stop patching symptoms and find the root cause of flaky tests?▼

Stop patching flaky tests by enforcing evidence-driven tracing across components. Gather reproducible data, analyze failure patterns, and test hypotheses systematically to isolate the actual root cause rather than applying superficial test fixes.

Does systematic debugging work for complex system integrations and performance anomalies?▼

Systematic debugging works for complex system integrations and performance anomalies by requiring traceability across components. It enforces an evidence-driven approach to diagnose intricate failures and prevent symptom-driven patches in production environments.

What is the best way to add defense-in-depth validations after fixing a bug?▼

The best way to add defense-in-depth validations is during the Implementation phase. After tracing the root cause, add multi-layer validations and progressive hardening across the system to prevent future regressions and ensure long-term stability.

Why does my software fix keep failing in production despite passing tests?▼

Production fixes fail when you patch symptoms instead of root causes. Systematic debugging resolves this by requiring evidence gathering, pattern analysis, and multi-layer validations before implementation, ensuring the underlying failure is fully eliminated.