What problem does it solve? Go codebases often ship with missing, inconsistent, or superficial comments that fail code review and confuse maintainers. This Skill enforces Google's Go style guide so every package, exported symbol, and unexported implementation detail carries complete, precise documentation. ## Core Features & Use Cases - Complete Comment Standards: Rules for package docs, exported types, interfaces, methods, struct fields, sentinel errors, and deprecation notices, all starting with the identifier name and written as full sentences. - Private Code Coverage: Guidance for documenting unexported types, helper functions, mutex ownership, and concurrency preconditions such as "caller must hold mu". - Review Checklist: A pre-submission checklist covering first-word rules, locking annotations, error taxonomy, and godoc rendering. - Use Case: When refactoring a Go service before a team review, activate this Skill to rewrite sparse comments into enterprise-grade godoc with concurrency guarantees and error conditions clearly stated. ## Quick Start Ask the AI to document your Go file or package following the Google style guide, for example by requesting full godoc comments for all exported and unexported symbols in a given source file.
