better-coding-debug
避免盲目试错，适合修复失败测试或构建错误。
系统化进行根因优先的调试流程，定位并验证错误与失败的真实原因。
遇到失败的测试、构建错误或行为异常时，按“先找根因再修复”的流程来调试：先把根因调查清楚（这是修复前的硬门），然后做模式分析、实施单一且经验证的修复，最后确认问题彻底解决并写复盘防止复现。必须在改动前完成根因定位，禁止盲目猜测式打补丁。优点是用故障前后可复现的测试证明修复有效，减少回归风险。
▸ 展开 SKILL.md 英文原文
Debug any bug, test failure, build break, error, or unexpected behaviour with a root-cause-first process that blocks guess-and-check patching. MUST be used whenever something is broken or a fix is attempted — a failing test, a build error, behaviour that does not match expectations, a performance regression — even if the user does not explicitly say debug, and especially when tempted to just try something. Four phases: root-cause investigation (hard gate before any fix), pattern analysis, a single tested fix at the root cause, verification that it holds — plus a post-mortem to prevent recurrence. Trigger: /better-coding-debug
帮我安装这个 skill：https://raw.githubusercontent.com/janschachtschabel/better-coding-skills/main/skills/better-coding-debug/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/janschachtschabel/better-coding-skills/main/skills/better-coding-debug/SKILL.md"# Better Coding Debug The process that turns "let me try changing this and see" into "I know exactly why it broke." Random fixes waste time, mask the real cause, and breed new bugs. Under pressure the instinct is to patch the symptom; this skill exists precisely for that moment. **Primary objective:** find and fix the *root cause*, proven by a test that failed before the fix and passes after — not a symptom silenced by a guess. **Core principle:** always find the root cause before attempting a fix. A symptom fix is a failure, even if the symptom goes away. --- ## Activation Begin the first response after loading with exactly this line: ▸ better-coding-debug active — root cause before f