systematic-debugging

Enforce a four-phase root-cause investigation workflow before proposing fixes.

Updated Jan 31, 2026
Ready to run
npx skills add https://github.com/shynlee04/idumb-plugin --skill systematic-debugging-shynlee04
💬 Prompt for ChatGPT / Claude Chat▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/shynlee04/idumb-plugin/tree/main/.agents/skills/systematic-debugging
Command: npx skills add https://github.com/shynlee04/idumb-plugin --skill systematic-debugging-shynlee04

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly and safely solving bugs by avoiding knee-jerk patches and ensuring root-cause investigation precedes any fix.

Core Features & Use Cases

  • Four-phase debugging workflow (Root Cause Investigation → Pattern Analysis → Hypothesis & Testing → Implementation)
  • Anti-patterns and red flags to prevent rushed fixes
  • Defense-in-depth guidance: validation at entry, business logic, environment, and debug instrumentation
  • Practical references and examples to accelerate troubleshooting

Quick Start

Install and run this skill to start a disciplined debugging workflow that prevents symptom fixes.

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 systematically debug a production incident instead of rushing a patch?▼

The best way to debug a production incident is to follow a structured root-cause investigation workflow that delays fixes until pattern analysis and hypothesis testing are complete. This prevents knee-jerk patches that only address symptoms.

How do I find the root cause of a test failure before attempting a code fix?▼

To find the root cause of a test failure, execute a four-phase debugging workflow: investigate the root cause, analyze patterns, test hypotheses, and only then implement the fix. This enforces discipline against rushed solutions.

How do I use stack traces to guide my debugging process?▼

Use stack traces during the root cause investigation and pattern analysis phases to trace execution paths and pinpoint failure origins. This guides your hypothesis testing before you proceed to the implementation phase.

What are common anti-patterns and red flags to avoid during root-cause investigation?▼

Common anti-patterns to avoid during root-cause investigation include applying symptom fixes without validation and skipping defense-in-depth checks. Recognizing these red flags prevents rushed fixes and ensures thorough pattern analysis.

Can I apply a systematic debugging workflow to integration problems and operations issues?▼

Yes, you can apply this systematic debugging workflow to any technical issue across development and operations, including production incidents, test failures, and integration problems. It enforces structured phases regardless of the context.

How do I implement defense-in-depth validation when diagnosing bugs?▼

Implement defense-in-depth validation by checking at the entry point, business logic, environment, and debug instrumentation levels. This multi-layer validation ensures your root-cause investigation covers all potential failure modes.