systematic-debugging

Investigate root causes through a four-phase debugging workflow.

4|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/atxinsky/skills --skill systematic-debugging-atxinsky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/atxinsky/skills/tree/main/systematic-debugging
Command: npx skills add https://github.com/atxinsky/skills --skill systematic-debugging-atxinsky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Debugging provides a disciplined approach to diagnosing and resolving bugs by focusing on root causes rather than patching symptoms, reducing firefighting and rework.

Core Features & Use Cases

  • Four-phase process: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation, ensuring thorough analysis before fixes.
  • Defenses against shortcuts: explicit rules to prevent skipping steps and to resist time-pressure rationalizations.
  • Use Case: when a production bug appears or tests fail, follow the process to identify the real trigger, trace data flow, and implement robust fixes.

Quick Start

Use the systematic-debugging skill to structure a bug investigation from error observation to root-cause resolution.

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 production bug instead of just patching symptoms?

To find the root cause of a production bug, follow a systematic debugging process that enforces cross-layer tracing and evidence gathering during a Root Cause Investigation phase before proposing any fixes.

What is the best way to debug failing tests and unexpected software behavior?

The best way to debug failing tests is to apply a four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation, ensuring thorough analysis before applying code changes.

How does a phased debugging workflow prevent symptom-driven repairs?

A phased debugging workflow prevents symptom-driven repairs by requiring the completion of Phase 1 root cause analysis before allowing any fixes, using explicit rules to resist time-pressure rationalizations and shortcuts.

When do I need to use systematic debugging for tracing data flow?

You need to use systematic debugging for tracing data flow when production bugs appear, tests fail, or unexpected behavior occurs, ensuring you identify the real trigger rather than applying superficial patches.

What are the limitations of fixing bugs without a structured debug trace?

Fixing bugs without a structured debug trace leads to firefighting and rework because it skips pattern analysis and hypothesis testing, resulting in symptom-driven repairs that fail to resolve the underlying root cause.