systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
定位
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
核心流程/章节
- Overview
- The Iron Law
- When to Use
- The Four Phases
- Red Flags - STOP and Follow Process
- your human partner's Signals You're Doing It Wrong
- Common Rationalizations
- Quick Reference
原文要点
Systematic Debugging
Overview
Random fixes waste time and create new bugs. Quick patches mask underlying issues.
Core principle: ALWAYS find root cause before attempting fixes. Symptom fixes are failure.
Violating the letter of this process is violating the spirit of debugging.
The Iron Law
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
If you haven't completed...
适用场景
- 基于 description 推断：Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
参见
- GitHub: superpowers