Debug Mantra

0•

Enforces a disciplined four-step debugging methodology to reliably reproduce, trace, falsify, and resolve complex software defects.

Debug Mantra instills a rigorous, evidence-first troubleshooting discipline into Claude Code to eliminate premature fixes and shotgun debugging. Before proposing code changes, Claude recites and follows four structured steps: establishing a deterministic reproduction, methodically tracing the fail path (via debuggers, knob enumeration, or isolated instrumentation), actively attempting to falsify candidate hypotheses before testing them, and maintaining a ledger of breadcrumbs across all experimental runs. This skill is indispensable when tackling evasive edge cases, flaky test failures, obscure stack traces, or attribution questions where identifying ground-truth state is essential.

주요 기능

01Flaky failure amplification guidelines to turn inconsistent bugs into reliable pass/fail signals
02Session breadcrumb ledger tracking every experiment to prevent circular reasoning and forgotten outcomes
03Hierarchical fail-path tracing spanning debuggers, knob enumeration, and uniquely tagged instrumentation
04Structured four-step protocol enforcing evidence and deterministic reproduction before code changes
05Rigorous hypothesis falsification prioritizing quick disproof over speculative confirmation
060 GitHub stars

사용 사례

01Preventing premature or cosmetic patches by verifying root causes through repeatable fail paths
02Diagnosing attribution problems to track down where an unexpected event, payload, or log originated
03Investigating elusive crashes, flaky integration tests, and production error logs systematically