systematic-debugginglisted

Use whenever the user asks to debug, diagnose, investigate, troubleshoot, or fix a bug, failing or flaky test, build error, performance regression, integration mismatch, or unexpected technical behavior; establish root cause before proposing changes.
blackstone2333/goldilocks · ★ 0 · AI & Automation · score 68

Install: claude install-skill blackstone2333/goldilocks

# Systematic Debugging Read [diagnose.md](../goldilocks/references/diagnose.md). Reproduce, trace the real flow and boundaries, form one falsifiable hypothesis, and fix the shared cause rather than symptoms. Read [prove.md](../goldilocks/references/prove.md) before claiming the issue fixed. After three failed hypotheses, stop patching and reassess. If only diagnosis was requested, report evidence and do not implement.