What problem does it solve? Go programs fail in subtle ways — typed-nil interfaces, shadowed error variables, goroutine leaks, and race conditions that pass tests but crash in production. This Skill enforces a systematic debugging methodology that finds the actual root cause instead of applying symptom-masking fixes. ## Core Features & Use Cases - Systematic Debugging Methodology: A 10-step process covering reproduction, hypothesis testing, root-cause tracing, and defense-in-depth, with a quick decision tree mapping symptoms to the right diagnostic path. - Common Go Pitfall Catalog: Documented patterns for nil pointer dereferences, interface nil gotchas, defer-in-loop leaks, concurrent map access, WaitGroup misuse, JSON float64 surprises, and more — each with reproductions and fixes. - Diagnostic Tooling Guidance: Practical references for pprof profiling (CPU, heap, goroutine, mutex, block), the race detector, GODEBUG tracing, Delve debugger, and production debugging with proper pprof authentication. - Use Case: A Go service intermittently crashes with 'concurrent map read and map write' despite recover middleware. The Skill explains why this fatal error bypasses recover, then guides you to protect the map with sync.RWMutex and confirm with go test -race. ## Quick Start Ask the agent to debug your Go issue, for example: my Go server hangs under load, help me find the root cause using this troubleshooting skill.
