Bug Hunter

c-kick/bug-hunter

> Proactive bug-hunting methodology — autonomous codebase reconnaissance to find latent bugs, hidden failure modes, and ticking time bombs BEFORE they detonate in production. Use this skill whenever the user asks to "find bugs", "hunt for issues", "audit this codebase", "what could go wrong", "find what's broken", "stress-test this project", "find landmines", "what will bite me later", or any variation of proactive defect discovery. Also trigger when the user says "scan for problems", "pre-flight check", "what am I missing across the codebase", "find the weak spots", or asks for a proactive quality sweep before a release, merge, or deployment. This is NOT for debugging known errors (use systematic-debugging) or reviewing specific code you're handed (use hostile-review). This is for when there are no known errors yet and you need to go FIND them.