systematic_debugging

Breaks down bug-finding into four phases: preparation, detection, root-cause analysis, and remediation.

Updated Aug 23, 2026

Search Tags:#testing #debugging #investigation #root cause #troubleshooting #bug fixing

Ready to run

npx skills add https://github.com/diegogalmarini/EscriAR --skill systematic-debugging-diegogalmarini

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill prevents wasted time and new bugs caused by quick fixes or symptom-based solutions. It enforces a rigorous, step-by-step process to ensure the true root cause of any issue is identified and addressed before any fixes are implemented.

Core Features & Use Cases

Mandatory Root Cause Analysis: Enforces a 4-phase process (Investigation, Pattern Analysis, Hypothesis, Implementation) that must be completed before proposing fixes.
Pressure Resistance: Includes specific language and structural defenses to prevent rationalization and shortcuts, especially under time pressure.
Anti-Pattern Identification: Clearly lists common rationalizations and behaviors that lead to ineffective fixes.
Use Case: When a critical bug appears in production, this Skill guides the engineer through a systematic investigation, ensuring the underlying issue is found and fixed, rather than applying a temporary patch that might break something else.

Quick Start

Use the systematic_debugging skill to investigate any unexpected behavior or test failure.

Frequently Asked Questions about systematic_debugging

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

FAQPage Schema

What is the best way to find the root cause of a bug instead of just fixing the symptom?▼

Root cause identification requires a structured four-phase methodology: investigation, pattern analysis, hypothesis formation, and implementation. This enforces evidence gathering and data flow tracing to prevent wasted time on ineffective symptom patches.

How do I debug complex systems without taking shortcuts under time pressure?▼

Debugging complex systems under time pressure requires structural defenses against rationalization. By following a strict investigation and hypothesis formation process, you resist quick fixes and ensure the true root cause is addressed before implementing changes.

How do I stop rationalization when troubleshooting critical production bugs?▼

To stop rationalization during troubleshooting, follow an anti-pattern identification process. Recognizing common rationalizations that lead to ineffective fixes enforces a rigorous, step-by-step investigation before any code changes are proposed.

When should I use a systematic debugging methodology for bug fixing?▼

You should use a systematic debugging methodology when a critical bug appears and quick fixes might introduce new issues. It ensures the underlying root cause is found through evidence gathering rather than applying temporary patches.

Does systematic debugging work for investigating unexpected behavior in complex systems?▼

Yes, systematic debugging works for complex systems by detailing evidence gathering and data flow tracing techniques. It guides engineers through pattern analysis and hypothesis formation to resolve unexpected behaviors effectively.

What are common anti-patterns that lead to ineffective bug fixes?▼

Common anti-patterns include applying quick fixes and symptom-based solutions driven by time pressure. Identifying these rationalizations ensures you complete a rigorous investigation and root cause analysis before implementing any fixes.