systematic-debugging

Diagnose software bugs through a four-phase root-cause investigation process.

Updated Jan 24, 2026

Search Tags:#debugging #defense-in-depth #systematic #phases #root-cause #traceback

Ready to run

npx skills add https://github.com/PaulPio/FinFlow- --skill systematic-debugging-paulpio

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a disciplined, four-phase framework to identify root causes of bugs and prevent symptom-focused fixes, reducing rework and time-to-resolution.

Core Features & Use Cases

Four-Phase Process: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation, completed in sequence.
Defensive Practices: Encourages defense-in-depth, explicit failure modes, and anti-pattern awareness to resist rushed fixes.
Traceability & Best Practices: Includes root-cause tracing and references to standard debugging techniques for debugging complex systems.
Use Case: When faced with production bugs, flaky tests, or performance regressions, follow the skill to uncover the true cause before changing code.

Quick Start

Begin by reading the skill, then perform Phase 1: Root Cause Investigation, reproduce the issue, gather evidence, and form a testable hypothesis.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is root-cause debugging and how does it prevent symptom fixes?▼

Root-cause debugging systematically identifies the true origin of bugs through evidence gathering and hypothesis testing, preventing superficial symptom fixes that lead to rework and recurring issues.

How do I debug flaky tests and production bugs systematically?▼

Debug flaky tests and production bugs using a four-phase process: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation, completing each phase sequentially before advancing.

Can I use this systematic debugging approach for performance regressions?▼

Yes, this systematic debugging approach applies to performance regressions across software systems, enforcing root-cause tracing and pattern analysis to uncover the true cause before changing code.

What's the best way to reproduce a technical issue before fixing it?▼

The best way to reproduce a technical issue is starting with Phase 1: Root Cause Investigation, where you gather evidence, reproduce the issue, and form a testable hypothesis before applying fixes.

Why does applying quick symptom fixes lead to recurring bugs?▼

Quick symptom fixes fail because they bypass pattern analysis and hypothesis testing, ignoring defense-in-depth practices and anti-pattern guidance needed to resolve the underlying root cause.