systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: ferranguardia

Identify root causes before implementing fixes across software bugs and incidents.

Updated Mar 2, 2026

Search Tags:#debugging #defense-in-depth #quality-assurance #phases #root-cause #software-engineering

Ready to run

npx skills add https://github.com/FerranGuardia/claude-autonomous-setup --skill systematic-debugging-ferranguardia

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/FerranGuardia/claude-autonomous-setup/tree/main/skills/methodology/systematic-debugging
Command: npx skills add https://github.com/FerranGuardia/claude-autonomous-setup --skill systematic-debugging-ferranguardia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging helps teams avoid symptom fixes by forcing root-cause investigation before changes.

Core Features & Use Cases

Four-phase workflow (Root Cause Investigation, Pattern Analysis, Hypothesis Testing, Implementation) that enforces a disciplined approach.
Defense-in-depth integration by adding validations and traceability to prevent regression.
Use Case: in a fast-moving bug, follow Phase 1 to identify the actual root cause and prevent recurring issues.

Quick Start

Read the skill overview and then execute Phase 1 through Phase 4 in sequence to ensure root causes are found before fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

How do I identify the root cause of a software bug instead of just patching the symptom?▼

Root-cause debugging enforces a four-phase investigation workflow before implementing fixes. By systematically analyzing patterns and testing hypotheses across multi-layer architectures, it ensures the actual source is fixed rather than just the visible symptom.

What is the best way to debug CI pipeline failures and flaky tests systematically?▼

Systematic debugging applies a four-phase workflow to CI failures and flaky tests. It moves from root-cause investigation through pattern analysis and hypothesis testing, concluding with implementation and defense-in-depth validations to prevent future regressions.

How does defense-in-depth integration work when fixing production incidents?▼

Defense-in-depth integration works by adding validations and traceability during the implementation phase of fixing production incidents. This practice prevents future regressions by ensuring multiple layers of error handling guard the corrected code path.

Can I use this systematic debugging approach for complex multi-layer architecture issues?▼

Yes, this systematic debugging approach applies to multi-layer architecture issues. The root-cause investigation phase is specifically designed to trace defects across different layers and components before applying any targeted fixes.

When should I avoid root-cause debugging and just apply a quick patch?▼

You should avoid root-cause debugging only when a fast-moving bug requires an immediate mitigation. However, you must still return to the four-phase workflow later to identify the actual root cause and prevent the recurring issue.