domains / families / software-engineering / golang-troubleshooting

golang-troubleshooting

separate

Troubleshoot Golang programs systematically - find and fix the root cause. Use when encountering bugs, crashes, deadlocks, races, or unexpected behavior in Go code. Covers debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve, race detection, GODEBUG tracing, and production debugging. Start here for any 'something is wrong' situation. Not for interpreting profiles or benchmarking (→ See `samber/cc-skills-golang@golang-benchmark` skill), applying optimization patterns (→ See `samber/cc-skills-golang@golang-performance` skill), or designing new code (→ See `samber/cc-skills-golang@golang-safety` skill for defensive coding, `samber/cc-skills-golang@golang-concurrency` skill for concurrency design).

When to use

• debugging methodology
• common Go pitfalls
• test-driven debugging
• pprof setup and capture
• Delve
• race detection
• GODEBUG tracing
• production debugging

When not to use

• interpreting profiles
• benchmarking
• applying optimization patterns
• designing new code
• defensive coding
• concurrency design

Skill page

Source