systematic-debugging

Guide a four-phase process to identify root causes of software bugs.

Updated Jan 10, 2026

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

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill prevents wasted time and new bugs by ensuring that the root cause of any issue is identified and addressed before any fixes are implemented. It combats the tendency to apply quick patches that only address symptoms.

Core Features & Use Cases

Structured Debugging Process: Guides users through four distinct phases: Investigation, Pattern Analysis, Hypothesis, and Implementation.
Root Cause Mandate: Emphasizes finding the fundamental issue, not just the immediate symptom.
Pressure Resistance: Includes specific language and rules to prevent shortcuts under time pressure or when a quick fix seems obvious.
Use Case: When a critical API endpoint starts returning errors, instead of immediately trying to restart services or tweak configurations, this Skill ensures a systematic investigation to find the underlying code or configuration flaw.

Quick Start

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

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

To find the root cause of a software bug, use a structured debugging process with four phases: Investigation, Pattern Analysis, Hypothesis, and Implementation. This enforces a root cause mandate to prevent applying quick patches that only address symptoms.

What is the best way to troubleshoot unexpected API endpoint errors systematically?▼

The best way to troubleshoot unexpected API errors is through systematic investigation rather than immediately restarting services. Follow a structured four-phase process to identify the underlying code or configuration flaw before implementing any fixes.

How do I resist pressure to apply quick fixes during critical bug fixing?▼

To resist pressure during critical bug fixing, follow a structured debugging process that includes specific anti-patterns and rationalizations. These rules prevent taking shortcuts under time pressure when a quick fix seems obvious.

Why should I avoid applying multiple fixes at once when troubleshooting unexpected behavior?▼

Avoiding multiple fixes at once during troubleshooting ensures you accurately identify the root cause. Applying simultaneous patches obscures which change actually resolved the issue and risks introducing new bugs.

What are the four phases of a systematic debugging process?▼

The four phases of a systematic debugging process are Investigation, Pattern Analysis, Hypothesis, and Implementation. This structured approach ensures thorough investigation before any code or configuration changes are implemented.

When do I need a structured process for bug fixing and troubleshooting?▼

You need a structured process for bug fixing when you encounter unexpected behaviors and want to prevent wasted time. It is essential when quick patches might introduce new bugs or fail to address the fundamental issue.