What problem does it solve? Go developers frequently misuse context.Context by creating fresh Background contexts mid-request, leaking resources from un-cancelled derived contexts, or storing contexts in structs, which breaks cancellation chains and loses trace data. ## Core Features & Use Cases - Propagation Discipline: Enforces taking ctx as the first parameter and propagating the caller's context through the entire call chain instead of recreating it. - Cancellation & Timeouts: Covers WithCancel, WithTimeout, WithDeadline, AfterFunc, and WithoutCancel with mandatory deferred cancel patterns. - Request-Scoped Values & Tracing: Shows how to carry trace IDs and request metadata under unexported key types and propagate them across HTTP services. - Use Case: When reviewing a Go HTTP handler that calls a database and spawns goroutines, use this Skill to verify the request context reaches QueryContext calls and that background work detaches via context.WithoutCancel. ## Quick Start Review my Go HTTP handler and service layer to check that context is propagated correctly with proper timeouts and cancellation.