systematic-debugging

Guide engineers through a four-phase debugging process to identify root causes.

4|1|Updated Apr 4, 2024

Search Tags:#debugging #troubleshooting #defense-in-depth #systematic #root-cause #pattern-analysis

Ready to run

npx skills add https://github.com/maraxen/praxis --skill systematic-debugging-maraxen

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Systematic Debugging provides a disciplined framework to identify the root cause of bugs before patching, preventing symptom-focused fixes and reducing rework.

Core Features & Use Cases

Four-Phase workflow (Root Cause Investigation → Pattern Analysis → Hypothesis & Testing → Implementation) to structure debugging.
Anti-patterns and defensive practices that resist time pressure and quick fixes.
Reference patterns and guidance for tracing data flow, defense-in-depth, and instrumentation to improve reliability across environments.

Quick Start

Initiate a four-phase debugging session to identify the root cause before implementing any fix.

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 symptoms?▼

To find a root cause, you must complete a structured root cause investigation before proposing any fixes. This prevents symptom-focused patches by guiding you through pattern analysis and testable hypotheses to ensure reliable resolution.

What is the best way to systematically debug a production incident?▼

Systematically debugging a production incident requires a four-phase workflow: root cause investigation, pattern analysis, hypothesis testing, and implementation with layered defenses. This structured process ensures rapid, reliable fixes under time pressure.

How do I trace data flow to identify the root cause of a software bug?▼

Tracing data flow to identify a root cause involves analyzing execution patterns and forming testable hypotheses based on evidence. Using reference patterns for instrumentation helps gather the necessary data to pinpoint the exact failure point.

Can I use systematic debugging for testing and development environments, not just production?▼

Yes, systematic debugging applies to software development, testing, and production incidents. The four-phase process ensures reliable fixes across all environments by enforcing root cause identification before implementing any code changes.

Why should I avoid quick fixes when troubleshooting software bugs?▼

Avoiding quick fixes during troubleshooting prevents symptom-focused patches that lead to rework. A systematic approach resists time pressure, ensuring you identify the actual root cause and implement layered defenses for long-term reliability.

How do I implement defense-in-depth when fixing a bug?▼

Implementing defense-in-depth during a fix involves applying layered defenses and gathering evidence after forming a testable hypothesis. This defensive practice improves reliability and prevents similar bugs from causing future incidents.