This one walks you through documenting Go projects the right way: godoc comments that explain why and when (not just what), README structure with the right section order, CONTRIBUTING and CHANGELOG files, and Example tests that actually help. It knows the difference between library and application documentation needs, and can parallelize work across packages using sub-agents when you're documenting a large codebase. Treats documentation as a first-class deliverable, which is refreshing. Built by samber, part of a larger Go skills collection, and it cross-references his naming and testing skills where relevant.
npx skills add https://github.com/samber/cc-skills-golang --skill golang-documentation