systematic-debugging

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

Updated Feb 11, 2026

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

Ready to run

npx skills add https://github.com/jayantrohila57/e-commerce --skill systematic-debugging-jayantrohila57

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/jayantrohila57/e-commerce/tree/main/.windsurf/skills/systematic-debugging
Command: npx skills add https://github.com/jayantrohila57/e-commerce --skill systematic-debugging-jayantrohila57

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 caused by quick fixes or symptom-based solutions, ensuring that the true root cause of any technical issue is identified and resolved.

Core Features & Use Cases

Structured Debugging Process: Guides users through a mandatory four-phase process (Investigation, Pattern Analysis, Hypothesis, Implementation) to systematically uncover the root cause of bugs, test failures, or unexpected behavior.
Pressure Resistance: Includes specific language and structural defenses to prevent rationalization and shortcuts, especially 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 thorough investigation into why the error is occurring, preventing recurring issues and ensuring a stable fix.

Quick Start

Use the systematic debugging skill when encountering any bug or unexpected behavior.

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

To find the root cause of a bug, follow a systematic debugging process involving investigation, pattern analysis, hypothesis formation, and implementation. This prevents wasted time on symptom-based workarounds and new bugs.

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

The best way to troubleshoot recurring API errors is a systematic debugging process that investigates why the error occurs before implementing fixes. This prevents recurring issues by identifying the true root cause rather than tweaking configurations.

How do I step through a systematic debugging process for unexpected behavior?▼

Step through systematic debugging by completing four phases: investigate the issue, analyze patterns, form a hypothesis, and implement the fix. This structured approach ensures thorough error resolution before any code changes.

How can I prevent quick fixes and shortcuts when debugging under time pressure?▼

To prevent quick fixes under time pressure, use a debugging process with structural defenses and specific language that resists rationalization. This ensures you identify the true root cause before applying any temporary workarounds.

Why does my bug fix keep causing new issues in my system?▼

Bug fixes cause new issues when they address symptoms rather than the root cause. A systematic debugging process prevents this by guiding you through thorough investigation and hypothesis testing before implementing any fixes.

When should I use a systematic debugging process instead of restarting services?▼

Use systematic debugging when encountering any bug, test failure, or unexpected behavior to ensure a stable fix. Restarting services or tweaking configurations often masks the true root cause, leading to recurring technical issues.