Implements a rigorous four-phase framework to identify root causes and resolve complex bugs without guesswork.
This skill provides a disciplined engineering workflow for troubleshooting technical issues, moving away from 'guess-and-check' patches toward scientific root cause analysis. It guides the debugging process through four mandatory phases: evidence-based investigation, pattern analysis, hypothesis testing, and test-driven implementation. By enforcing the 'Iron Law' of understanding the root cause before proposing any code changes, this skill helps developers solve persistent test failures, production bugs, and architectural flaws more efficiently while preventing the introduction of secondary regressions.
Key Features
01Evidence gathering protocols for multi-component systems (CI, Build, API, DB)
02Integration with Test-Driven Development (TDD) for verified, permanent resolutions
03Four-phase scientific debugging framework: Investigation, Analysis, Hypothesis, and Implementation
040 GitHub stars
05Mandatory root cause tracing to prevent symptom-masking 'quick fixes'
06Architectural review triggers that stop 'fix-thrashing' after three failed attempts
Use Cases
01Debugging deep data flow issues across multi-layered architectures and service boundaries
02Resolving recurring regression bugs where previous attempts failed to address the underlying problem
03Identifying the source of non-deterministic or flaky test failures in complex CI/CD pipelines
