G

golang-context

by @samberv
4.6(34)

Go context.Contextの標準的な使用法。キャンセルシグナル、タイムアウト、リクエストスコープの値を伝播し、ゴルーチンリークやリソース未解放を回避。

concurrencybackend-developmenttimeout-handlingcancellationgoroutine-managementGitHub
インストール方法
npx skills add https://github.com/samber/cc-skills-golang --skill golang-context
compare_arrows

Before / After 効果比較

1
使用前

Context の手動管理は、キャンセルチェックの見落としにつながりやすく、バックグラウンドの Goroutine が終了できなくなる原因となります。1つの HTTP サービスエンドポイントで数百の Goroutine がリークする可能性があり、その特定には数時間かかります。

使用後

正しい Context の伝播とキャンセル処理コードを自動生成し、タイムアウト後にすべてのリソースが確実にタイムリーに解放されるようにすることで、サービス全体のリーク問題を10分で修正します。

SKILL.md

golang-context

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.

Best Practices Summary

  • The same context MUST be propagated through the entire request lifecycle: HTTP handler → service → DB → external APIs

  • ctx MUST be the first parameter, named ctx context.Context

  • NEVER store context in a struct — pass explicitly through function parameters

  • NEVER pass nil context — use context.TODO() if unsure

  • cancel() MUST always be deferred immediately after WithCancel/WithTimeout/WithDeadline

  • context.Background() MUST only be used at the top level (main, init, tests)

  • Use context.TODO() as a placeholder when you know a context is needed but don't have one yet

  • NEVER create a new context.Background() in the middle of a request path

  • Context value keys MUST be unexported types to prevent collisions

  • Context values MUST only carry request-scoped metadata — NEVER function parameters

  • Use context.WithoutCancel (Go 1.21+) when spawning background work that must outlive the parent request

Creating Contexts

Situation Use

Entry point (main, init, test) context.Background()

Function needs context but caller doesn't provide one yet context.TODO()

Inside an HTTP handler r.Context()

Need cancellation control context.WithCancel(parentCtx)

Need a deadline/timeout context.WithTimeout(parentCtx, duration)

Context Propagation: The Core Principle

The most important rule: propagate the same context through the entire call chain. When you propagate correctly, cancelling the parent context cancels all downstream work automatically.

// ✗ Bad — creates a new context, breaking the chain
func (s *OrderService) Create(ctx context.Context, order Order) error {
    return s.db.ExecContext(context.Background(), "INSERT INTO orders ...", order.ID)
}

// ✓ Good — propagates the caller's context
func (s *OrderService) Create(ctx context.Context, order Order) error {
    return s.db.ExecContext(ctx, "INSERT INTO orders ...", order.ID)
}

Deep Dives

Cancellation, Timeouts & Deadlines — How cancellation propagates: WithCancel for manual cancellation, WithTimeout for automatic cancellation after a duration, WithDeadline for absolute time deadlines. Patterns for listening (<-ctx.Done()) in concurrent code, AfterFunc callbacks, and WithoutCancel for operations that must outlive their parent request (e.g., audit logs).

Context Values & Cross-Service Tracing — Safe context value patterns: unexported key types to prevent namespace collisions, when to use context values (request ID, user ID) vs function parameters. Trace context propagation: OpenTelemetry trace headers, correlation IDs for log aggregation, and marshaling/unmarshaling context across service boundaries.

Context in HTTP Servers & Service Calls — HTTP handler context: r.Context() for request-scoped cancellation, middleware integration, and propagating to services. HTTP client patterns: NewRequestWithContext, client timeouts, and retries with context awareness. Database operations: always use *Context variants (QueryContext, ExecContext) to respect deadlines.

Cross-References

  • → See the samber/cc-skills-golang@golang-concurrency skill for goroutine cancellation patterns using context

  • → See the samber/cc-skills-golang@golang-database skill for context-aware database operations (QueryContext, ExecContext)

  • → See the samber/cc-skills-golang@golang-observability skill for trace context propagation with OpenTelemetry

  • → See the samber/cc-skills-golang@golang-design-patterns skill for timeout and resilience patterns

Enforce with Linters

Many context pitfalls are caught automatically by linters: govet, staticcheck. → See the samber/cc-skills-golang@golang-linter skill for configuration and usage. Weekly Installs748Repositorysamber/cc-skills-golangGitHub Stars1.1KFirst SeenMar 22, 2026Security AuditsGen Agent Trust HubPassSocketPassSnykPassInstalled onopencode712cursor706codex702gemini-cli700github-copilot699cline698

ユーザーレビュー (0)

レビューを書く

効果
使いやすさ
ドキュメント
互換性

レビューなし

統計データ

インストール数32.7K
評価4.6 / 5.0
バージョン
更新日2026年7月9日
比較事例1 件

ユーザー評価

4.6(34)
5
76%
4
24%
3
0%
2
0%
1
0%

この Skill を評価

0.0

対応プラットフォーム

🔧Claude Code

タイムライン

作成2026年4月9日
最終更新2026年7月9日
🎁 Agent 知識カード
アンケート