What problem does it solve? Go code written by developers or generated by AI often violates core language idioms — swallowed errors, broken error chains, misplaced interfaces, and unstructured logging. This Skill enforces idiomatic sequential Go 1.26 patterns so code reviews and implementations follow community-accepted conventions. ## Core Features & Use Cases - Error handling patterns: Explicit if err != nil checks, %w wrapping, sentinel and typed errors, errors.Join aggregation, and the Go 1.26 generic errors.AsType inspection. - Structured logging with slog: Handler selection (JSON vs Text), attributes, groups, LogValuer redaction, dynamic levels, and allocation-free LogAttrs hot paths. - Generics and Go 1.26 features: Type parameters, self-referential constraints, new(expr) initialization, and go fix modernizers. - Interface and style guidance: Consumer-side interfaces, value-vs-pointer receivers, naming conventions, and LLM anti-pattern detection. - Use Case: When reviewing a Go service that discards errors with _ = err and defines an IUserRepository interface next to its only implementation, use this Skill to rewrite the error strategy with %w wrapping and move the interface to the consumer package. ## Quick Start Ask the agent to review or write sequential Go code following idiomatic error handling, slog logging, and interface conventions, for example: review my user package for idiomatic Go error handling and logging.
