golang-concurrency

Golang concurrency patterns. Use when writing or reviewing concurrent Go code — goroutines, channels, select, locks, sync primitives, errgroup, singleflight, worker pools, fan-out/fan-in — or for goroutine leaks, race conditions, channel ownership, or choosing channels vs mutexes.

الانتقال إلى التثبيت

المستودع: context-labs/whip
آخر نشاط في المصدر: ٢٤ أغسطس ٢٠٢٦ في ٠٤:١٥
لغة SKILL.md المكتشفة: الإنجليزية
النجوم: ٢٠٥
التفرعات: ٢١

خيارات التثبيت

يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.

npx skills add https://github.com/context-labs/whip --skill golang-concurrency

يبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.

تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.

مراجعة ملفات المصدر

اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.

مستكشف الملفات

5 ملفات

SKILL.md

تعليمات المصدر · معاينة للقراءة فقط

العودة إلى البحث العودة إلى التثبيت

Go Concurrency Best Practices

Go's concurrency model is built on goroutines and channels. Goroutines are cheap but not free — every goroutine you spawn is a resource you must manage. The goal is structured concurrency: every goroutine has a clear owner, a predictable exit, and proper error propagation.

Core Principles

Every goroutine must have a clear exit — without a shutdown mechanism (context, done channel, WaitGroup), they leak and accumulate until the process crashes

Share memory by communicating — channels transfer ownership explicitly; mutexes protect shared state but make ownership implicit

Send copies, not pointers on channels — sending pointers creates invisible shared memory, defeating the purpose of channels

Only the sender closes a channel — closing from the receiver side panics if the sender writes after close

Specify channel direction (chan<-, <-chan) — the compiler prevents misuse at build time

Default to unbuffered channels — larger buffers mask backpressure; use them only with measured justification

Always include ctx.Done() in select — without it, goroutines leak after caller cancellation

Go Concurrency Best Practices

Core Principles

Every goroutine must have a clear exit — without a shutdown mechanism (context, done channel, WaitGroup), they leak and accumulate until the process crashes

Share memory by communicating — channels transfer ownership explicitly; mutexes protect shared state but make ownership implicit

Send copies, not pointers on channels — sending pointers creates invisible shared memory, defeating the purpose of channels

Only the sender closes a channel — closing from the receiver side panics if the sender writes after close

Specify channel direction (chan<-, <-chan) — the compiler prevents misuse at build time

Default to unbuffered channels — larger buffers mask backpressure; use them only with measured justification

Always include ctx.Done() in select — without it, goroutines leak after caller cancellation

name	golang-concurrency
description	Golang concurrency patterns. Use when writing or reviewing concurrent Go code — goroutines, channels, select, locks, sync primitives, errgroup, singleflight, worker pools, fan-out/fan-in — or for goroutine leaks, race conditions, channel ownership, or choosing channels vs mutexes.
user-invocable	true
license	MIT
compatibility	Designed for Claude Code, Codex or similar harness, and for projects using Golang.
metadata	{"author":"samber","version":"1.2.0","openclaw":{"emoji":"⚡","homepage":"https://github.com/samber/cc-skills-golang","requires":{"bins":"[Truncated]"},"install":[]}}
allowed-tools	Read Edit Write Glob Grep Bash(go:) Bash(golangci-lint:) Bash(git:*) Agent AskUserQuestion
paths	["*/.go"]

name	golang-concurrency
description	Golang concurrency patterns. Use when writing or reviewing concurrent Go code — goroutines, channels, select, locks, sync primitives, errgroup, singleflight, worker pools, fan-out/fan-in — or for goroutine leaks, race conditions, channel ownership, or choosing channels vs mutexes.
user-invocable	true
license	MIT
compatibility	Designed for Claude Code, Codex or similar harness, and for projects using Golang.
metadata	{"author":"samber","version":"1.2.0","openclaw":{"emoji":"⚡","homepage":"https://github.com/samber/cc-skills-golang","requires":{"bins":"[Truncated]"},"install":[]}}
allowed-tools	Read Edit Write Glob Grep Bash(go:) Bash(golangci-lint:) Bash(git:*) Agent AskUserQuestion
paths	["*/.go"]

Scenario	Use	Why
Passing data between goroutines	Channel	Communicates ownership transfer
Coordinating goroutine lifecycle	Channel + context	Clean shutdown with select
Protecting shared struct fields	`sync.Mutex` / `sync.RWMutex`	Simple critical sections
Simple counters, flags	`sync/atomic`	Lock-free, lower overhead
Many readers, few writers on a map	`sync.Map`	Optimized for read-heavy workloads. Concurrent map read/write causes a hard crash
Caching expensive computations	`sync.Once` / `singleflight`	Execute once or deduplicate

Need	Use	Why
Wait for goroutines, errors not needed	`sync.WaitGroup`	Fire-and-forget
Wait + collect first error	`errgroup.Group`	Error propagation
Wait + cancel siblings on first error	`errgroup.WithContext`	Context cancellation on error
Wait + limit concurrency	`errgroup.SetLimit(n)`	Built-in worker pool

Primitive	Use case	Key notes
`sync.Mutex`	Protect shared state	Keep critical sections short; never hold across I/O
`sync.RWMutex`	Many readers, few writers	Never upgrade RLock to Lock (deadlock)
`sync/atomic`	Simple counters, flags	Prefer typed atomics (Go 1.19+): `atomic.Int64`, `atomic.Bool`
`sync.Map`	Concurrent map, read-heavy	No explicit locking; use `RWMutex`+map when writes dominate
`sync.Pool`	Reuse temporary objects	Always `Reset()` before `Put()`; reduces GC pressure
`sync.Once`	One-time initialization	Go 1.21+: `OnceFunc`, `OnceValue`, `OnceValues`
`sync.WaitGroup`	Waiting for simple goroutines	Go 1.25+: prefer `wg.Go(func(){ ... })` for fire-and-wait tasks that do not panic and do not need error propagation. For Go <1.25 use `Add`/`Done`. For errors/cancellation/limits, use `errgroup` with context.
`x/sync/singleflight`	Deduplicate concurrent calls	Cache stampede prevention
`x/sync/errgroup`	Goroutine group + errors	`SetLimit(n)` replaces hand-rolled worker pools

golang-concurrency

خيارات التثبيت

مراجعة ملفات المصدر

Go Concurrency Best Practices

Core Principles

Go Concurrency Best Practices

Core Principles

Channel vs Mutex vs Atomic

WaitGroup vs errgroup

Sync Primitives Quick Reference

Concurrency Checklist

Pipelines and Worker Pools

Parallelizing Concurrency Audits

Common Mistakes

Cross-References

Go 1.26 experimental goroutine leak profile

References

Mistake	Fix
Fire-and-forget goroutine	Provide stop mechanism (context, done channel)
Closing channel from receiver	Only the sender closes
`time.After` in hot loop	Reuse `time.NewTimer` + `Reset`
Missing `ctx.Done()` in select	Always select on context to allow cancellation
Unbounded goroutine spawning	Use `errgroup.SetLimit(n)` or semaphore
Sharing pointer via channel	Send copies or immutable values
`wg.Add` inside goroutine	Call `Add` before `go` — `Wait` may return early otherwise
Forgetting `-race` in CI	Always run `go test -race ./...`
Mutex held across I/O	Keep critical sections short

golang-concurrency

معلومات المصدر

خيارات التثبيت

مراجعة ملفات المصدر

المزيد من هذا المستودع

المزيد من هذا المستودع

Go Concurrency Best Practices

Core Principles

Go Concurrency Best Practices

Core Principles

Channel vs Mutex vs Atomic

WaitGroup vs errgroup

Sync Primitives Quick Reference

Concurrency Checklist

Pipelines and Worker Pools

Parallelizing Concurrency Audits

Common Mistakes

Cross-References

Go 1.26 experimental goroutine leak profile

References