菜单
Apply 4-phase root cause debugging methodology when user encounters errors, bugs, test failures, or unexpected behavior in code. Trigger when user mentions "bug", "error", "failing", "not working", "debug", or shares error messages. Use systematic approach rather than guess-and-check.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Monitors analysis-doc lifecycle in all three lanes — EMERGING→PRODUCTION promotion, PRODUCTION→RETIRING/RETIRED retirement (replacement-readiness as robust community/vendor elements mature), and follow-lane upkeep (followed canons' advance triggers + liveness, per ABSORPTION-MAP.md)
Validates new analysis documents against project quality standards. Trigger when user adds an analysis doc or says "review analysis".
Ensures SOURCES.md stays synchronized when adding new analysis documents or sources. Trigger when user adds a new analysis doc, says "update sources", "add source", or after pattern-reviewer identifies missing source entries. Enforces evidence tier classification and proper citation format.
Analyze recent git commits in a target project to surface patterns, identify improvement opportunities, and generate recommendations weighted by source authority and recency. Trigger when user says "analyze commits", "review my recent work", "what patterns do you see", or when evaluating a project for best-practice alignment.
Updates analysis documents with new version requirements and dependencies when Claude Code releases new features
Apply comprehensive quality review when user prepares content for publication (blog posts, articles, documentation, presentations). Trigger when user mentions "publish", "post", "article", "review this", "draft complete", "ready to share". Enforce evidence-based claims, intellectual honesty, professional voice, and balanced perspective.
| name | systematic-debugger |
| description | Apply 4-phase root cause debugging methodology when user encounters errors, bugs, test failures, or unexpected behavior in code. Trigger when user mentions "bug", "error", "failing", "not working", "debug", or shares error messages. Use systematic approach rather than guess-and-check. |
| allowed-tools | Read, Grep, Glob, Bash |
Replace ad-hoc debugging with systematic REPRODUCE-ISOLATE-UNDERSTAND-FIX protocol.
🔗 Production Framework: For advanced debugging with strict enforcement, see obra/superpowers which provides production-grade debugging frameworks and multi-agent orchestration patterns. This skill demonstrates Claude Code skill integration of systematic debugging principles.
Activate: Bug reports, error messages, stack traces, test failures, "not working", "broken", "debug", "why is this happening?"
Skip: Design/planning phase, theoretical discussions, trivial errors (typos, missing imports)
Confirm problem exists. Get exact error message, trigger conditions, frequency, last known working state.
Narrow problem space. Binary search through code, add instrumentation, find minimal failing case. Identify: logic, data, timing, environment, integration, or assumption error.
Root cause analysis. Form hypothesis → predict evidence → test → confirm/reject. Ask: WHY does this happen, not just WHAT.
Fix root cause (not symptom). Add regression test. Run full test suite. Check for similar issues elsewhere.
Phase 1: Reproduction Confirmed
- Error: [exact message]
- Trigger: [conditions]
- Files: [file:line]
Phase 2: Problem Isolated
- Root location: [file:line]
- Problem type: [logic/data/timing/environment/integration/assumption]
Phase 3: Root Cause Identified
- Why it happens: [explanation]
- Blast radius: [what else affected]
Phase 4: Fix Validated
✅ Problem resolved
✅ Regression test added
✅ All tests pass
✅ Similar issues checked