systematic-debugging

Trace bugs to root causes through call chains and data flow.

7|1|Updated Feb 14, 2026

Search Tags:#debugging #defense-in-depth #trace #root-cause #data-flow #incident-analysis

Ready to run

npx skills add https://github.com/fratilanico/apex-os-bad-boy --skill systematic-debugging-fratilanico

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/fratilanico/apex-os-bad-boy/tree/main/systematic-debugging
Command: npx skills add https://github.com/fratilanico/apex-os-bad-boy --skill systematic-debugging-fratilanico

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Debugging provides a disciplined, root-cause-first approach to diagnosing bugs, preventing symptom fixes, and speeding reliable resolutions.

Core Features & Use Cases

Structured four-phase workflow that guides teams from root-cause investigation to safe implementation.
Root-cause tracing, pattern analysis, hypothesis testing, and defensive validation across multi-component systems.
Defense-in-depth techniques that add validations at entry, business logic, environment, and instrumentation layers.

Quick Start

Walk me through the full debugging process, applying Phase 1 through Phase 4 to a given issue.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

How do I trace a bug to its root cause instead of just fixing the symptom?▼

Trace bugs to root causes by following failures through the full call chain and data flow. A structured four-phase workflow guides you from observation and pattern analysis to hypothesis testing and safe implementation.

What is the best way to debug flaky behavior in multi-component systems?▼

Debug flaky behavior in multi-component systems by tracing data flow across components and collecting evidence. Pattern analysis and hypothesis testing isolate intermittent failures rather than masking them with retries.

How do I add defense-in-depth validations when fixing a production incident?▼

Add defense-in-depth validations at entry, business logic, environment, and instrumentation layers. This ensures incident analysis captures root causes while preventing regression across the full call chain.

Can I use this systematic debugging approach for both test failures and production issues?▼

Yes, systematic debugging spans tests, production, and flaky behavior in multi-component systems. It enforces root-cause investigation and instrumentation techniques regardless of the execution environment.

What are the four phases of the systematic debugging workflow?▼

The four phases are root cause investigation, pattern analysis, hypothesis testing, and implementation. This structured approach ensures evidence collection and data flow tracing before applying any fix.