systematic-debugging

系统化调试

来源：obra/superpowers

概述

此技能提供了一套结构化的调试方法，避免随机猜测，并确保在解决问题之前充分理解问题。

4 阶段调试流程

阶段 1：复现

修复之前，先可靠地复现问题。

## Reproduction Steps
1. [Exact step to reproduce]
2. [Next step]
3. [Expected vs actual result]

## Reproduction Rate
- [ ] Always (100%)
- [ ] Often (50-90%)
- [ ] Sometimes (10-50%)
- [ ] Rare (<10%)

阶段 2：隔离

缩小问题来源的范围。

## Isolation Questions
- When did this start happening?
- What changed recently?
- Does it happen in all environments?
- Can we reproduce with minimal code?
- What's the smallest change that triggers it?

阶段 3：理解

找出根本原因，而不只是表面症状。

## Root Cause Analysis
### The 5 Whys
1. Why: [First observation]
2. Why: [Deeper reason]
3. Why: [Still deeper]
4. Why: [Getting closer]
5. Why: [Root cause]

阶段 4：修复并验证

修复问题，并验证它确实已解决。

## Fix Verification
- [ ] Bug no longer reproduces
- [ ] Related functionality still works
- [ ] No new issues introduced
- [ ] Test added to prevent regression

调试清单

## Before Starting
- [ ] Can reproduce consistently
- [ ] Have minimal reproduction case
- [ ] Understand expected behavior

## During Investigation
- [ ] Check recent changes (git log)
- [ ] Check logs for errors
- [ ] Add logging if needed
- [ ] Use debugger/breakpoints

## After Fix
- [ ] Root cause documented
- [ ] Fix verified
- [ ] Regression test added
- [ ] Similar code checked

常用调试命令

# Recent changes
git log --oneline -20
git diff HEAD~5

# Search for pattern
grep -r "errorPattern" --include="*.ts"

# Check logs
pm2 logs app-name --err --lines 100

反模式

❌ 随意更改 - “也许改一下这个就行……” ❌ 忽视证据 - “不可能是这个原因” ❌ 想当然 - 没有证据就认定“肯定是 X” ❌ 不先复现 - 盲目修复 ❌ 只处理表面症状 - 没有找出根本原因