This skill enforces a rigorous, evidence-first approach to software debugging, moving beyond 'guess-and-check' methods to ensure every fix is backed by data. It guides users through a systematic workflow: collecting evidence, isolating variables, formulating hypotheses, and implementing fixes only after a root cause is identified. By requiring a failing test case before any code change, it ensures that the actual problem is solved and prevents regressions, making it essential for resolving complex crashes, intermittent failures, and performance bottlenecks.
主要功能
01Failing test-driven development (TDD) for bug verification
02Structured stage tracking using the maintain-tasks integration
03Mandatory root cause identification before proposing solutions
042 GitHub stars
05Built-in 'circuit breaker' to escalate after three failed hypotheses
06Four-stage evidence-based investigation framework
