systematic-debugging

Diagnose software bug root causes through four investigation phases.

3|Updated Nov 19, 2025

Search Tags:#workflow #debugging #investigation #root cause #problem solving #troubleshooting #bug fix

Ready to run

npx skills add https://github.com/seanGSISG/crispy-claude --skill systematic-debugging-seangsisg

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Randomly applying fixes or addressing symptoms instead of root causes leads to wasted time, new bugs, and recurring issues. This skill provides a disciplined, four-phase framework to ensure thorough understanding before attempting solutions.

Core Features & Use Cases

Root Cause Investigation: Guides through careful error message analysis, consistent reproduction, and evidence gathering in multi-component systems.
Pattern Analysis: Compares broken code with working examples and references to identify key differences and dependencies.
Hypothesis Testing: Enforces forming a single, testable hypothesis and making minimal changes to verify it.

Quick Start

Use the systematic-debugging skill to investigate why the 'user-login' test is failing intermittently.

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

Root cause debugging systematically investigates why a failure occurs by analyzing error messages, reproducing the issue consistently, and gathering evidence before proposing fixes. This four-phase framework—investigation, pattern analysis, hypothesis testing, and implementation—ensures you address underlying causes rather than surface symptoms, preventing recurring bugs.

What's the best way to diagnose intermittent failures and production bugs in multi-component systems?▼

Systematic debugging guides you through careful error analysis, consistent reproduction across components, and evidence comparison with working references. It enforces completing root-cause investigation first, then pattern analysis to identify key differences and dependencies before forming and testing a single, minimal hypothesis.

How do I investigate performance issues and integration problems using a structured approach?▼

Performance and integration problems require phase-specific investigation: gather reproducible evidence, compare broken code against working examples, form a testable hypothesis, then make minimal changes to verify it. This workflow prevents wasted fixes and ensures the underlying cause is resolved, not just the visible symptom.

Why does applying random fixes lead to new bugs and recurring issues?▼

Addressing symptoms without understanding root causes creates technical debt and cascading failures. Systematic debugging enforces anti-shortcut rules and phase-specific checklists that require thorough investigation and minimal, hypothesis-driven changes, ensuring fixes are repeatable and lasting.

Can I use this debugging framework for test failures, production bugs, and performance issues?▼

Yes. Systematic debugging covers test failures, production bugs, performance issues, and integration problems through a unified four-phase framework. Phase 1 completion is mandatory before proposing fixes, ensuring consistent, root-cause-driven investigation across all failure types.