What problem does it solve? Writing Go code that is merely functional is easy, but writing idiomatic Go that is maintainable, efficient, and consistent with community conventions requires deep knowledge of patterns that are easy to get wrong, such as goroutine leaks, improper error wrapping, and poorly designed interfaces. ## Core Features & Use Cases - Error Handling Guidance: Enforces error wrapping with context, sentinel errors, custom error types, and correct use of errors.Is and errors.As. - Concurrency Patterns: Provides worker pools, context-based cancellation, graceful shutdown, errgroup coordination, and goroutine leak prevention. - Design Conventions: Covers interface design, package organization, functional options, struct embedding, and performance optimizations like sync.Pool and slice preallocation. - Use Case: When reviewing a Go pull request, activate this Skill to check that errors are wrapped with context, goroutines handle cancellation properly, and interfaces are defined where they are consumed. ## Quick Start Review my Go service code and refactor it to follow idiomatic Go patterns for error handling and concurrency.