systematic-debugging

SKILL.md

Find the root cause before writing fixes. Understanding why something breaks leads to correct fixes. Guessing wastes time and creates new problems.

Core principle: If you can't explain WHY it's broken, you're not ready to fix it. Every fix must address a specific, understood root cause.

Use for any technical issue: test failures, build errors, bugs, unexpected behavior, performance problems. Especially valuable when previous attempts haven't worked or when tempted to try a "quick fix."

在調試錯誤、測試失敗、意外行為或需要在修復之前找到根本原因時使用 來源：technickai/ai-coding-config。

查看原文