systematic-debugging

Guide systematic four-phase debugging with root cause analysis and failing tests.

1|2|Updated Mar 6, 2026

Search Tags:#testing #debugging #troubleshooting #root cause analysis #validation #bug fixing

Ready to run

npx skills add https://github.com/cinjoff/fhhs-skills --skill systematic-debugging-cinjoff

💬 Prompt for ChatGPT / Claude Chat▼

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

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 guesswork when encountering technical issues. It enforces a rigorous, systematic approach to debugging.

Core Features & Use Cases

Root Cause Analysis: Guides you through identifying the fundamental reason for a bug, not just its symptoms.
Phased Investigation: Breaks down debugging into distinct, mandatory phases: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation.
Error Prevention: Emphasizes creating failing tests before implementing fixes and validating at multiple layers to make bugs impossible.
Use Case: When a test fails unexpectedly, instead of trying random code changes, you use this Skill to meticulously trace the data flow, identify the exact point of failure, form a hypothesis, write a specific test case, and then implement a targeted fix.

Quick Start

Use the systematic-debugging skill to investigate any bug or test failure by following its four-phase process.

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

Finding the root cause of a bug requires a systematic four-phase process: thorough investigation, pattern analysis, hypothesis testing, and targeted implementation with failing test cases.

What is the best way to debug failing tests without introducing new bugs?▼

The best way to debug failing tests is to trace data flow, form a hypothesis, write a specific failing test case before fixing code, and validate at multiple layers for defense-in-depth.

How do I stop random guesswork when troubleshooting unexpected software errors?▼

Troubleshooting unexpected software errors effectively means following a phased investigation process that mandates pattern analysis and hypothesis testing before any code changes are implemented.

Why should I write a failing test case before implementing a bug fix?▼

Writing a failing test case before implementing a bug fix ensures the root cause is accurately targeted, validates the fix works, and prevents regression errors in your software.

Can I use systematic debugging for any software development bug?▼

Yes, this systematic debugging approach is applicable to general software development, ensuring robust and reliable code by enforcing rigorous root cause analysis across any technical issue.

What are the limitations of systematic debugging for urgent production incidents?▼

Systematic debugging mandates thorough investigation and pattern analysis before fixes, which requires time and may not suit urgent production incidents needing immediate, temporary patches.