systematic-debugging

Guide root cause analysis through investigation, pattern analysis, hypothesis, and implementation phases.

Updated Dec 4, 2025

Search Tags:#debugging #root cause #troubleshooting #bug fixing #error analysis #systematic process

Ready to run

npx skills add https://github.com/hiroto0701/dotfiles --skill systematic-debugging-hiroto0701

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill prevents wasted time and new bugs by ensuring you find the true root cause of any issue before attempting fixes, especially under pressure.

Core Features & Use Cases

Structured Debugging: Guides you through a 4-phase process (Investigation, Pattern Analysis, Hypothesis, Implementation) to systematically uncover the origin of bugs.
Pressure Resistance: Provides explicit rules and anti-patterns to prevent rushing and fixing symptoms, even in emergencies.
Use Case: When a critical API is down, instead of applying a quick, temporary fix, use this Skill to ensure you identify and resolve the underlying architectural flaw, preventing future outages.

Quick Start

Use the systematic-debugging skill to investigate any bug or unexpected behavior you encounter.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is a systematic debugging process for finding root causes?▼

Systematic debugging is a structured four-phase methodology for root cause analysis, guiding you through investigation, pattern analysis, hypothesis formation, and implementation to resolve software defects. It prevents symptom-fixing and ensures thoroughness under pressure.

How do I fix a critical production bug without just patching the symptom?▼

To fix a critical production bug without patching symptoms, follow a structured debugging methodology of investigation, pattern analysis, hypothesis formation, and implementation. This ensures you identify and resolve the underlying architectural flaw, preventing future outages.

What's the best way to troubleshoot unexpected software behaviors and test failures?▼

The best way to troubleshoot unexpected behaviors and test failures is applying a four-phase root cause analysis process. This methodology systematically uncovers the origin of bugs through investigation and hypothesis formation before attempting any code fixes.

Can I use a structured debugging methodology for performance problems and API outages?▼

Yes, you can use a structured debugging methodology for performance problems and API outages. It addresses issues ranging from test failures to production bugs by enforcing specific anti-pattern rules that prevent rushing to fix symptoms during emergencies.

Why does fixing symptoms instead of root causes create new bugs?▼

Fixing symptoms instead of root causes creates new bugs because it leaves the underlying defect unresolved. Without a systematic debugging process, applying quick temporary fixes under pressure often introduces new issues while failing to prevent future outages.