standards-go-concurrency

You prevent goroutine leaks by enforcing explicit ownership and context-based cancellation. This Skill codifies lifecycle management rules to ensure every goroutine has a clear termination path, stopping leaks before they occur in concurrent Go applications.

The best way to handle error propagation with bounded parallelism is using errgroup-based fan-out/fan-in patterns. This approach safely manages concurrent goroutines, limits parallel processing, and propagates errors back to the main routine efficiently.

You avoid data races by following proper mutex discipline and documenting thread-safety expectations. These standards provide concrete requirements for mutex usage to ensure reliable, testable concurrent code without data races.

You need context-aware cancellation when managing goroutine lifecycles and channel ownership. Applying context-first cancellation enables safe goroutine termination and prevents blocked channels from causing deadlocks or resource leaks.

Yes, you can apply these concurrency standards across code reviews and development tasks. They enforce concrete requirements for bounded fan-out, channel ownership, and leak prevention to evaluate and refactor critical paths reliably.