from cc-skills-golang1,476
Human-coded Go style guidelines for clarity, function design, control flow, and idiomatic practices — use when writing or reviewing Go code, creating linters, o
Provides a concise, opinionated set of Go coding conventions that go beyond automated formatters. This skill captures human judgment about naming, function design, error handling, line-breaking, composite literals, slice/map initialization, and when to prefer pointers vs values. It explains concrete examples and prescriptive MUST/SHOULD rules so an AI assistant or reviewer can suggest edits, refactors, or review comments aligned with idiomatic Go.
Invoke for code reviews, PR feedback, generating examples, or when the agent is asked to write Go code for production. Use it to craft review comments that emphasize clarity (reduce nesting, early returns), safe initializations (non-nil slices/maps), and maintainable function signatures (≤4 params or options structs). Also useful when configuring CI linters or creating coding standards docs.
Designed to be used by coding-capable assistants and CI review agents (Claude Code, Copilot/Code models, Cursor, Codex, Gemini CLI). The flavor is tailored for tools that can read code and produce diffs or review comments.
This skill has not been reviewed by our automated audit pipeline yet.
Go Data Structures
Authoritative guidance on choosing and using Go built-in and standard-library data structures, with practical best practices for slices, maps, arrays, container
samber/hot — In-memory Caching for Go
Guidance and patterns for using samber/hot in Go: eviction algorithms, TTL, loaders, sharding, stale-while-revalidate, and Prometheus monitoring.
