Back to Details

debugging

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Debugging Skills

调试技能

A collection of systematic debugging methodologies that ensure thorough investigation before attempting fixes.
一套系统化的调试方法论，确保在尝试修复前进行全面调查。

Available Sub-Skills

可用子技能

Systematic Debugging

系统化调试

Location: 
systematic-debugging/SKILL.md
Four-phase debugging framework: Root Cause Investigation → Pattern Analysis → Hypothesis Testing → Implementation. The iron law: NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST.
位置： 
systematic-debugging/SKILL.md
四阶段调试框架：根本原因调查 → 模式分析 → 假设测试 → 实施。铁律：未进行根本原因调查，绝不修复。

Root Cause Tracing

根本原因追踪

Location: 
root-cause-tracing/SKILL.md
Trace bugs backward through the call stack to find the original trigger. Don't fix symptoms - find where invalid data originated and fix at the source.
位置： 
root-cause-tracing/SKILL.md
通过调用栈反向追踪bug，找到原始触发点。不要修复症状——找到无效数据的源头并从根源修复。

Defense-in-Depth Validation

纵深防御验证

Location: 
defense-in-depth/SKILL.md
Validate at every layer data passes through to make bugs structurally impossible. Four layers: Entry Point → Business Logic → Environment Guards → Debug Instrumentation.
位置： 
defense-in-depth/SKILL.md
在数据流经的每一层进行验证，从结构上杜绝bug的发生。四个层级：入口点 → 业务逻辑 → 环境防护 → 调试工具。

Verification Before Completion

完成前验证

Location: 
verification-before-completion/SKILL.md
Run verification commands and confirm output before claiming success. The iron law: NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE.
位置： 
verification-before-completion/SKILL.md
在宣称成功前运行验证命令并确认输出。铁律：无新鲜验证证据，绝不宣称完成。

When to Use

使用场景

  • Bug in production → Start with systematic-debugging
  • Error deep in stack trace → Use root-cause-tracing
  • Fixing a bug → Apply defense-in-depth after finding root cause
  • About to claim "done" → Use verification-before-completion
  • 生产环境中的Bug → 从systematic-debugging开始
  • 堆栈跟踪深处的错误 → 使用root-cause-tracing
  • 修复Bug时 → 找到根本原因后应用纵深防御
  • 即将宣称“完成”时 → 使用verification-before-completion

Quick Dispatch

快速匹配

SymptomSub-Skill
Test failure, unexpected behaviorsystematic-debugging
Error appears in wrong locationroot-cause-tracing
Same bug keeps recurringdefense-in-depth
Need to confirm fix worksverification-before-completion
症状子技能
测试失败、意外行为systematic-debugging
错误出现在错误位置root-cause-tracing
同一Bug反复出现defense-in-depth
需要确认修复有效verification-before-completion

Core Philosophy

核心理念

"Systematic debugging is FASTER than guess-and-check thrashing."
From real debugging sessions:
  • Systematic approach: 15-30 minutes to fix
  • Random fixes approach: 2-3 hours of thrashing
  • First-time fix rate: 95% vs 40%
"系统化调试比盲目试错的效率更高。"
来自真实调试场景的数据：
  • 系统化方法：15-30分钟修复
  • 随机修复方法：2-3小时的无效尝试
  • 首次修复成功率：95% vs 40%