Golang Context

Teaches Claude how to handle context.Context idiomatically in Go: propagation through call chains, cancellation patterns, timeouts, and context values. The core principle is simple but easy to mess up: pass the same context through your entire request lifecycle, never create a fresh context.Background() mid-chain, and always defer cancel(). Covers the gotchas like when to use TODO() versus Background(), why you shouldn't store contexts in structs, and how to use context values without namespace collisions. Includes patterns for HTTP handlers, database calls, and cross-service tracing. Most useful when you're building services that need proper cancellation propagation or you keep getting context usage wrong in code reviews.

skills.sh installs: 42.7K
GitHub stars: 3.8K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add samber/cc-skills-golang --skill golang-context --agent claude-code

Installs into .claude/skills of the current project.

Files

Community default. A company skill that explicitly supersedes samber/cc-skills-golang@golang-context skill takes precedence.

Go context.Context Best Practices

context.Context is Go's mechanism for propagating cancellation signals, deadlines, and request-scoped values across API boundaries and between goroutines. Think of it as the "session" of a request — it ties together every operation that belongs to the same unit of work.