What problem does it solve? Go programs fail in subtle ways — nil pointer panics, race conditions, goroutine leaks, silent error swallowing — and guessing at fixes wastes time and creates new bugs. This Skill enforces a systematic, evidence-driven debugging methodology so you find the actual root cause instead of patching symptoms. ## Core Features & Use Cases - Systematic Debugging Methodology: A 10-step process with Golden Rules (reproduce before fixing, one hypothesis at a time, trace to root cause) plus a quick decision tree mapping symptoms to the right diagnostic path. - Common Go Bug Catalog: Documented pitfalls with reproduction patterns and fixes — interface nil gotcha, variable shadowing, defer-in-loop leaks, concurrent map access, JSON float64 surprises, and more. - Diagnostic Tooling Guidance: Practical references for pprof profiling (CPU, heap, goroutine, mutex, block), the race detector, GODEBUG tracing, Delve debugger, and production debugging with secure pprof setup. - Use Case: Your Go service intermittently crashes with 'concurrent map read and map write' despite recover() middleware. The Skill explains why this fatal error bypasses recover, and walks you through reproducing it with go test -race and fixing it with proper mutex synchronization. ## Quick Start Ask the agent to debug your Go issue, for example: my Go server hangs after a few hours, help me find the root cause using this troubleshooting skill.
