goroutine-leak-check

You can detect and fix goroutine leaks in Go applications by running automated code analysis with goleak, which identifies stuck goroutines and provides actionable fixes to restore memory efficiency.

A goroutine leak occurs when concurrent goroutines become stuck and are never terminated, leading to memory leaks; this Skill analyzes your Go code to identify these blocked routines and recommend fixes.

Yes, you need Go 1.26 or later to use this built-in goroutine leak analysis, which targets Go codebases utilizing concurrent patterns and relies on the uber-go/goleak dependency for detection.

To check for memory leaks with goleak, run the provided leak script command, which analyzes your concurrent Go code to find stuck goroutines and outputs guidance on how to fix the identified leak patterns.

The main limitation is that this goroutine leak detection requires Go 1.26 or later and is primarily designed for Go codebases that utilize concurrent patterns, meaning non-concurrent code will not benefit from this analysis.