systematic-debugging

Enforce a four-phase debugging process to identify root causes before fixes.

Updated Mar 29, 2026

Search Tags:#testing #debugging #anti-patterns #defense-in-depth #root-cause #phase-based

Ready to run

npx skills add https://github.com/Me1e/ralphthon --skill systematic-debugging-me1e

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Debugging guides engineers to identify root causes before applying fixes, reducing wasted time and preventing symptom-focused patches.

Core Features & Use Cases

Four-phase workflow including Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation to ensure comprehensive fixes.
Anti-patterns, defense-in-depth, and structured testing guidance to resist time pressure and avoid shortcuts.
Applicable to bugs, test failures, production incidents, performance issues, and integration problems across software projects.

Quick Start

Follow Phase 1 to begin root-cause investigation before proposing any fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is root-cause debugging and when should I use it for software issues?▼

Root-cause debugging identifies the actual origin of software issues before applying fixes. Use it for test failures, production incidents, flaky behavior, and performance problems to stop guesswork and prevent symptom-focused patches.

How do I debug a failing test using a structured phase-based process?▼

Debug failing tests through a four-phase process: investigate root causes first, analyze patterns, test hypotheses, then implement fixes. This structured approach resists time pressure and prevents shortcuts that mask the underlying issue.

What's the best way to stop guessing and find the actual cause of production incidents?▼

Stop guessing on production incidents by enforcing root-cause investigation before proposing any fixes. Analyze patterns, test hypotheses against the evidence, and apply defense-in-depth guidance to ensure comprehensive incident resolution.

Does systematic debugging work for flaky behavior and performance problems?▼

Yes, systematic debugging applies to flaky behavior and performance problems. It enforces pattern analysis and hypothesis testing to identify the root cause across all software issues, preventing unreliable symptom patches.

Why should I analyze anti-patterns and defense-in-depth during root-cause investigation?▼

Analyze anti-patterns and defense-in-depth during root-cause investigation to resist time pressure and avoid shortcuts. This ensures the final implementation fixes the actual bug and prevents future regressions.

How do I start root-cause investigation before proposing any code fixes?▼

Start root-cause investigation by following Phase 1 of the debugging workflow before proposing any fixes. This initial phase enforces a thorough examination of the software issue to stop guesswork and identify the true origin.