domains / families / software-engineering / golang-concurrency

golang-concurrency

separate

Golang concurrency design — goroutine lifecycle and leak prevention, channels and `select`, channel ownership and direction, `sync.Mutex`/`RWMutex`/`sync.Map`/`sync.Once`/atomics, `errgroup`, `singleflight`, worker pools, and fan-out/fan-in pipelines. Use when writing or reviewing concurrent Go code, when choosing between channels and mutexes, when protecting a shared map or counter, or when a goroutine has no clear exit. Not for defensive coding unrelated to concurrency such as nil panics, slice aliasing, or numeric overflow (→ See `samber/cc-skills-golang@golang-safety` skill), and not for debugging a specific hung, crashing, or racing program after the fact (→ See `samber/cc-skills-golang@golang-troubleshooting` skill).

When to use

• writing concurrent Go code
• reviewing concurrent Go code
• choosing between channels and mutexes
• protecting a shared map or counter
• preventing goroutine leaks
• designing worker pools
• designing fan-out/fan-in pipelines
• auditing concurrent code

When not to use

• defensive coding unrelated to concurrency
• nil panics
• slice aliasing
• numeric overflow
• debugging a specific hung program
• debugging a crashing program
• debugging a racing program

Skill page

Source