diagnosing-bugs

Diagnosing Bugs A discipline for hard bugs. Skip phases only when explicitly justified. When exploring the codebase, read CONTEXT.md (if it exists) to get a clear mental model of the relevant modules, and check ADRs in the area you're touching. Phase 1 — Build a feedback loop This is the skill. Everything else is mechanical. If you have a tight pass/fail signal for the bug — one that goes red on this bug — you will find the cause; bisection, hypothesis-testing, and instrumentation all just consume it. If you don't have one, no amount of staring at code will save you. Spend disproportionate effort here. Be aggressive. Be creative. Refuse to give up. Ways to construct one — try them in roughly this order Show more Installs 1.8K Repository mattpocock/skills GitHub Stars 132.4K First Seen 13 days ago Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Pass