systematic-debugging

Guide a 4-stage root cause analysis workflow for debugging code bugs.

1|1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/gaoqiongxie/skills-ai --skill systematic-debugging-gaoqiongxie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/gaoqiongxie/skills-ai/tree/main/systematic-debugging
Command: npx skills add https://github.com/gaoqiongxie/skills-ai --skill systematic-debugging-gaoqiongxie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the inefficiency of blind trial-and-error when debugging code bugs, system errors, and intermittent failures, which often leads to temporary fixes that don't address the true root cause and waste valuable development time.

Core Features & Use Cases

  • Structured 4-Stage Debugging Workflow: Guides users through hypothesis formation, evidence collection, root cause analysis, and fix verification to systematically resolve issues instead of random guessing.
  • Built-in Debugging Resources: Includes common bug type quick lookup tables, log/code/database debugging command snippets, and 5 whys analysis templates to speed up evidence gathering and root cause identification.
  • Use Case Example: When a user reports an API returning 500 errors, the skill guides them to form hypotheses about possible causes, collect log evidence to rule out incorrect assumptions, use 5 whys to trace the root cause to a missing database index causing slow queries that exhaust the connection pool, then verify the fix works without introducing regressions.

Quick Start

Use the systematic-debugging skill to guide me through resolving the intermittent 500 error that occurs when users submit orders on the e-commerce platform.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is root cause analysis in software debugging and when do I need it?▼

Root cause analysis in software debugging is a structured method to identify the true origin of code bugs and system errors. You need it when trial-and-error fixes fail to prevent recurring issues like intermittent failures or performance drops.

How do I fix intermittent API 500 errors without guessing?▼

To fix intermittent API 500 errors, follow a 4-stage workflow: form hypotheses, collect log evidence, trace the root cause using 5 whys analysis, and verify the fix. This prevents unnecessary code changes and resolves issues like missing database indexes.

Can I use a systematic debugging workflow for concurrency faults and null pointer exceptions?▼

Yes, a systematic debugging workflow applies to concurrency faults, null pointer exceptions, and performance issues. It guides you through evidence-based troubleshooting using log, code, and database command snippets to systematically resolve common production bugs.

What is the best way to troubleshoot production bugs versus using trial and error?▼

The best way to troubleshoot production bugs is evidence-based debugging. Unlike trial and error, it uses a structured 4-stage process of hypothesis formation, evidence collection, root cause analysis, and fix verification to minimize unnecessary code changes.

Why does my bug fix keep causing regressions in production?▼

Bug fixes cause regressions when they address symptoms rather than the root cause. Applying a 4-stage debugging workflow with fix verification ensures you validate evidence and test preventive measures, stopping recurring issues without introducing new faults.