systematic_debugging

Guide users through a four-phase root cause analysis process for bugs.

1|Updated Feb 24, 2026

Search Tags:#debugging #troubleshooting #root cause analysis #bug fixing #systematic process #error investigation

Ready to run

npx skills add https://github.com/FacuM/yolo-agent --skill systematic-debugging-facum

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic_debugging
Source: https://github.com/FacuM/yolo-agent/tree/main/.claude/skills/systematic-debugging
Command: npx skills add https://github.com/FacuM/yolo-agent --skill systematic-debugging-facum

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill prevents wasted time and new bugs caused by quick fixes or symptom-based solutions, ensuring that the true root cause of any technical issue is identified and resolved.

Core Features & Use Cases

Systematic Investigation: Guides users through a mandatory four-phase process (Investigation, Pattern Analysis, Hypothesis, Implementation) to ensure thorough root cause analysis.
Pressure Resistance: Includes specific language and structural defenses to prevent rationalization under time pressure or when a quick fix seems obvious.
Use Case: When a critical bug appears in production, use this Skill to systematically diagnose the issue, preventing the temptation to apply a superficial fix that might mask the real problem or introduce new errors.

Quick Start

Use the systematic debugging skill to investigate the current 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 a bug instead of just fixing the symptom?▼

A systematic debugging process prevents quick fixes by guiding you through investigation, pattern analysis, hypothesis testing, and verified implementation. It enforces evidence gathering and data flow tracing to ensure the true root cause is identified and resolved.

What is the best way to investigate unexpected behavior in complex systems?▼

The best way to investigate unexpected behavior in complex systems is using a structured debugging process that mandates evidence gathering and data flow tracing. This ensures thorough root cause analysis before implementing any fixes, avoiding new errors from superficial patches.

How do I resist the temptation to apply a quick fix during production troubleshooting?▼

To resist applying quick fixes during production troubleshooting, use a systematic debugging process with built-in pressure resistance. It provides structural defenses and specific rules to prevent rationalization when a symptom-based fix seems obvious under time pressure.

Can I use this systematic debugging process for test failures and error investigation?▼

Yes, you can use this systematic debugging process for test failures and error investigation. It guides you through identifying the root cause of bugs, test failures, or unexpected behavior by emphasizing thorough investigation and pattern analysis before implementing fixes.

When should I avoid quick fixes and mandate a systematic error investigation?▼

You should mandate a systematic error investigation when a critical bug appears in production or complex systems. Avoiding quick fixes prevents wasted time and ensures the true root cause is resolved, stopping superficial patches that might mask the real problem or introduce new errors.