systematic-debugging

Enforce a four-phase debugging methodology for root cause analysis.

2|Updated May 27, 2026

Search Tags:#testing #debugging #root cause #troubleshooting #systematic #reliability

Ready to run

npx skills add https://github.com/edlng/agents --skill systematic-debugging-edlng

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill eliminates the cycle of random, ineffective patches and time-wasting "guess-and-check" debugging by enforcing a rigorous, evidence-based investigation process.

Core Features & Use Cases

Four-Phase Framework: Guides you through Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation.
Anti-Shortcut Guardrails: Explicitly identifies and blocks common rationalizations like "I'm in a hurry" or "this is just a simple fix."
Use Case: When a production service experiences intermittent failures, use this skill to trace the data flow across component boundaries instead of blindly adding retry logic or timeouts.

Quick Start

Activate 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 intermittent production failures instead of guessing?▼

To find the root cause of intermittent production failures, apply an evidence-based investigation process that traces data flow across component boundaries rather than blindly adding retry logic or timeouts.

What is the best way to stop guess-and-check debugging for complex software bugs?▼

The best way to stop guess-and-check debugging is to enforce a rigorous four-phase methodology: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation, ensuring you validate before changing code.

How do I systematically debug test failures in my software engineering workflow?▼

To systematically debug test failures, activate a structured investigation framework that requires evidence-based hypothesis testing and architectural validation before implementing any code patches.

Can I use a systematic debugging process for performance problems and not just crashes?▼

Yes, you can use this systematic debugging process for complex system performance problems, as it enforces tracing data flow and validating hypotheses across component boundaries before applying fixes.

When should I not use a structured root cause analysis approach for troubleshooting?▼

You should not use structured root cause analysis when bypassing investigation for a quick patch, as anti-shortcut guardrails explicitly block rationalizations like "this is just a simple fix" to ensure reliability.

Does systematic debugging work without relying on random patches and timeouts?▼

Yes, systematic debugging works by eliminating random, ineffective patches through pattern analysis and hypothesis testing, forcing you to validate architectural boundaries instead of applying superficial fixes.