systematic-debugging

Debug technical issues through a four-phase root cause analysis process.

Updated Jan 8, 2026

Search Tags:#testing #debugging #investigation #root cause #troubleshooting #error handling

Ready to run

npx skills add https://github.com/AndyAnh174/BanThuoc-SEO --skill systematic-debugging-andyanh174

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/AndyAnh174/BanThuoc-SEO/tree/main/.agent/skills/systematic-debugging
Command: npx skills add https://github.com/AndyAnh174/BanThuoc-SEO --skill systematic-debugging-andyanh174

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 fixed, rather than just addressing the immediate symptom.

Core Features & Use Cases

Structured Investigation: Guides users through a mandatory four-phase process (Investigation, Pattern Analysis, Hypothesis, Implementation).
Pressure Resistance: Includes specific language and rules to prevent shortcuts under time pressure or when a quick fix seems obvious.
Use Case: When a test fails unexpectedly, instead of guessing or adding arbitrary delays, use this Skill to systematically trace the error back to its origin, ensuring a permanent fix.

Quick Start

Use the systematic-debugging skill to investigate the unexpected behavior in the user authentication flow.

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 failing test instead of just fixing the symptom?▼

To find the root cause of a failing test, follow a structured four-phase debugging process: Investigation, Pattern Analysis, Hypothesis, and Implementation. This methodology mandates evidence gathering and hypothesis testing to trace errors back to their origin rather than applying superficial symptom fixes.

What is the best way to systematically debug production bugs under time pressure?▼

Systematically debugging production bugs under time pressure requires a structured methodology with specific rules to prevent shortcuts. It ensures you gather evidence, analyze patterns, and test hypotheses before implementing any code changes, avoiding new bugs from rushed quick fixes.

How do I troubleshoot unexpected software behavior without guessing or adding arbitrary delays?▼

Troubleshooting unexpected software behavior without guessing requires a systematic investigation phase to gather evidence. By analyzing patterns and testing hypotheses before implementation, you ensure fixes are based on verified root causes rather than arbitrary workarounds like adding delays.

Can I use a systematic debugging methodology for performance problems and not just test failures?▼

Yes, you can use systematic debugging for performance problems, production bugs, and test failures. The four-phase methodology is applicable to all software development scenarios, ensuring consistent root cause analysis and verification before and after implementation across any technical issue.

Why does fixing symptoms instead of the root cause lead to new bugs?▼

Fixing symptoms instead of the root cause leads to new bugs because underlying issues remain unresolved and interact with code changes. A systematic debugging process prevents this by mandating thorough pattern analysis and hypothesis verification before you implement any modifications.