What problem does it solve? Writing Go code that follows community conventions is hard without a reference, leading to inconsistent error handling, goroutine leaks, and poorly designed packages that are difficult to maintain and review. ## Core Features & Use Cases - Error Handling Patterns: Error wrapping with context, custom error types, sentinel errors, and errors.Is/errors.As checking. - Concurrency Patterns: Worker pools, context-based cancellation and timeouts, graceful shutdown, errgroup coordination, and goroutine leak prevention. - Design Guidance: Interface design, functional options pattern, package organization, struct embedding, and performance techniques like sync.Pool and slice preallocation. - Use Case: When reviewing a Go pull request, activate this Skill to check whether the code wraps errors with context, handles goroutine cancellation properly, and follows standard project layout conventions. ## Quick Start Review my Go service code and suggest improvements based on idiomatic Go patterns for error handling and concurrency.
