cash-debug

Systematically debugs software defects through reproduction, isolation, root cause analysis, and evidence-based fixing with TDD.

1|Updated May 11, 2026
One-click install
npx skills add https://github.com/cashwu/Agentflow-SDD --skill cash-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cash-debug
Source: https://github.com/cashwu/Agentflow-SDD/tree/main/.agents/skills/cash-debug
Command: npx skills add https://github.com/cashwu/Agentflow-SDD --skill cash-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates guesswork and inefficient trial-and-error debugging by enforcing a rigorous, four-phase scientific workflow to identify and resolve software defects.

Core Features & Use Cases

  • Structured Workflow: Guides the user through Reproduce, Isolate, Root Cause, and Fix phases to ensure discipline.
  • Evidence-Based Resolution: Mandates failing test cases before applying fixes to prevent regressions and symptom-masking.
  • Use Case: When a complex bug causes intermittent crashes in a production environment, this skill helps the developer isolate the exact trigger and verify the fix through a controlled, repeatable process.

Quick Start

Invoke the cash-debug skill followed by a clear description of the bug you are currently experiencing to begin the systematic investigation process.

Frequently Asked Questions about cash-debug

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

FAQPage Schema
What is the best way to systematically debug intermittent software failures in a complex codebase?

Systematic debugging of intermittent failures requires a structured four-phase methodology: reproduce the defect, isolate the trigger, perform root cause analysis, and apply an evidence-based fix to ensure complete resolution.

How do I fix software bugs without masking the underlying symptoms or causing regressions?

To fix software bugs without masking symptoms, enforce an evidence-based resolution workflow that mandates writing a failing test case to confirm the root cause before applying any code modifications.

How to perform root cause analysis for a bug that is difficult to reproduce?

Root cause analysis for difficult bugs begins with the reproduction phase to consistently trigger the error, followed by isolating the exact code path causing the failure before attempting any fixes.

Does test-driven development help with troubleshooting software defects?

Test-driven development is essential for troubleshooting software defects because it mandates creating a failing test case that verifies the bug exists before a fix is applied, preventing future regressions.

What is the three-attempt rule in software debugging?

The three-attempt rule in software debugging is a constraint requiring disciplined investigation, limiting trial-and-error fixing attempts and enforcing structured root cause analysis before applying a code modification.

When should I use a systematic debugging workflow instead of trial and error?

You should use a systematic debugging workflow instead of trial and error whenever facing complex codebase defects, intermittent crashes, or bug regressions that require disciplined investigation and evidence-based fixing.