Enforces a rigorous, four-phase root cause analysis process to eliminate guesswork and prevent regression bugs.
This skill transforms the debugging process from trial-and-error into a scientific methodology. It mandates a strict protocol where the root cause must be identified and verified before any code changes are proposed. By following four structured phases—Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation—it ensures that technical issues are solved at their source rather than masked by superficial patches. This approach is particularly effective for complex multi-component systems, intermittent failures, and high-pressure environments where 'quick fixes' often lead to further instability.
主要功能
01Diagnostic instrumentation strategies for multi-component system boundaries
02Strict requirement for failing test cases before implementing any solution
