systematic-debugging

Enforce root-cause investigation before implementing fixes for technical incidents.

Updated Jan 22, 2026

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

Ready to run

npx skills add https://github.com/frydaiii/manbot --skill systematic-debugging-frydaiii

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/frydaiii/manbot/tree/main/.claude/skills/systematic-debugging
Command: npx skills add https://github.com/frydaiii/manbot --skill systematic-debugging-frydaiii

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Random fixes waste time and create new bugs. Quick patches mask underlying issues.

Violating the letter of this process is violating the spirit of debugging.

Core Features & Use Cases

Four-phase, methodical approach: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation.
Anti-shortcuts and explicit stop rules to resist time pressure.
Defense-in-depth guidance: validate data at multiple layers and add instrumentation for forensics.

Quick Start

Load the skill and complete Phase 1 before attempting any fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is systematic debugging and why should I trace root causes before fixing bugs?▼

Systematic debugging enforces root-cause investigation before applying fixes, preventing random patches that waste time and mask underlying software issues. It requires tracing data flow and completing all four investigation phases before implementation.

How do I debug production issues and test failures methodically without taking shortcuts?▼

Debug production issues methodically by applying explicit anti-shortcuts and stop rules. Complete Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation phases sequentially to resist time pressure and avoid creating new bugs.

What's the best way to find the root cause of performance problems and technical incidents?▼

The best way to find root causes of performance problems is tracing data flow across multiple layers. Add instrumentation for forensics, validate data at multiple layers, and establish a failing test before writing a fix.

When should I use a phase-based debugging process instead of applying quick patches?▼

Use a phase-based debugging process whenever facing software bugs, test failures, or production issues to prevent quick patches from creating new bugs. Violating this methodical process violates the spirit of effective debugging.

Does defense-in-depth debugging work for complex software bugs and test failures?▼

Defense-in-depth debugging works for complex software bugs by validating data at multiple layers and adding instrumentation for forensics. This approach ensures thorough root-cause investigation before moving to hypothesis testing and implementation.