Enforces a rigorous, four-phase root cause analysis process before any code fixes are proposed or implemented.
This skill transforms the debugging process from 'guess-and-check' thrashing into a scientific, evidence-based workflow. It mandates a strict protocol where developers must investigate root causes, analyze patterns, and form hypotheses before writing a single line of fix code. By requiring diagnostic instrumentation in multi-component systems and architectural questioning after repeated failures, it ensures that underlying issues are permanently resolved rather than masked by temporary patches, significantly increasing first-time fix rates.
主な機能
011 GitHub stars
02Enforces 'Root Cause Investigation' as a mandatory precursor to code changes.
03Guides users through backward data flow tracing to find original bug triggers.
04Includes a 'Three-Strike Rule' to identify and address fundamental architectural flaws.
05Implements diagnostic logging across multi-component system boundaries.
06Integrates with TDD to ensure failing tests are created before any fix is applied.
ユースケース
01Resolving persistent bugs where previous 'quick fixes' have failed to stick.
02Debugging intermittent production failures or complex race conditions.
03Investigating 'mysterious' build or CI/CD integration issues across environments.
