Enforce context.Context as the first parameter across Go call chains.
npx skills add https://github.com/phant-app/phant --skill go-context-phant-app
Please help me install this Agent Skill. Skill: go-context Source: https://github.com/phant-app/phant/tree/main/.agents/skills/go-context Command: npx skills add https://github.com/phant-app/phant --skill go-context-phant-app
Go projects often struggle with structuring and propagating cancellation, deadlines, and values across API boundaries. This Skill provides patterns for using context.Context effectively, ensuring first-parameter context, avoiding embedding contexts in structs, and avoiding custom Context types, with guidance on where to attach data and how to derive and propagate context safely.
Refactor code to pass context.Context as the first parameter across the call chain and remove embedded or custom contexts.
High-intent search queries and answers about installing and using this skill.
Pass context.Context as the first parameter in functions and methods to propagate it through the call chain. This convention ensures deadlines, cancellations, and values flow correctly across API boundaries without storing context in structs.
Storing context in structs breaks cancellation propagation and makes lifecycle management unpredictable. Context should flow explicitly through function parameters, ensuring derived timeouts and cancellation signals reach background workers and API handlers safely.
Derive deadlines and cancellations by creating child contexts from parent contexts using built-in functions. This ensures that when a parent context is canceled, all derived child contexts are automatically canceled, propagating termination signals across modular packages.
No, avoid creating custom context types. Use the standard context.Context interface to ensure compatibility and safe value extraction. Custom implementations risk breaking cancellation propagation and traceability across background workers and API boundaries.
Attach values using context.WithValue and extract them safely using type-safe key extraction. This ensures traceability data flows across function calls without violating the convention of keeping context as the first parameter and avoiding struct storage.
skeletorfletIdentify and apply idiomatic Go patterns for Go 1.22+ projects.
ozan-fnExplain context.Context usage for cancellation, propagation, and request-scoped values in Golang.
tamago0224Analyzes Go concurrency code to fix goroutine leaks, race conditions, and channel ownership.
jovermierEnforce context-first signatures and goroutine lifecycle management in Go code.
