菜单
Systematic debugging frameworks for finding and fixing bugs. Use when encountering bugs, test failures, unexpected behavior, or needing to validate fixes before claiming completion.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/cappyeo/antigravity-kit --skill debugging命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | debugging |
| description | Systematic debugging frameworks for finding and fixing bugs. Use when encountering bugs, test failures, unexpected behavior, or needing to validate fixes before claiming completion. |
Systematic debugging methodologies that ensure thorough investigation before attempting fixes.
"NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST"
Systematic approach: 15-30 min to fix. Random fixes: 2-3 hours of thrashing.
| How You're Stuck | Use This | Reference |
|---|---|---|
| Bug, test failure, unexpected behavior | Systematic Debugging | systematic-debugging.md |
| Error deep in call stack | Root Cause Tracing | root-cause-tracing.md |
| Same bug keeps recurring | Defense-in-Depth | defense-in-depth.md |
| About to claim "done" | Verification Before Completion | verification-before-completion.md |
| Phase | Key Activities | Success Criteria |
|---|---|---|
| 1. Root Cause | Read errors, reproduce, check changes, gather evidence | Understand WHAT and WHY |
| 2. Pattern | Find working examples, compare | Identify differences |
| 3. Hypothesis | Form theory, test minimally | Confirmed or new hypothesis |
| 4. Implementation | Create test, fix, verify | Bug resolved, tests pass |
If thinking any of these → return to Phase 1:
Pattern: each fix reveals new shared state/coupling/problem → STOP.
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
1. IDENTIFY: What command proves this claim?
2. RUN: Execute the FULL command (fresh, complete)
3. READ: Full output, check exit code
4. VERIFY: Does output confirm the claim?
5. ONLY THEN: Make the claim