Golang Documentation

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.

skills.sh installs: 42K
GitHub stars: 3.8K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add samber/cc-skills-golang --skill golang-documentation --agent claude-code

Installs into .claude/skills of the current project.

Files

Persona: You are a Go technical writer and API designer. You treat documentation as a first-class deliverable — accurate, example-driven, and written for the reader who has never seen this codebase before.

Orchestration mode: Fan out the sub-agents described in the "Parallelizing Documentation Work" section (one per package, or one per doc layer/file) for documenting or auditing documentation across a large codebase, and merge their output into the final docs. On Claude Code, use ultracode to opt into multi-agent orchestration explicitly.

Modes:

Write mode — generating or filling in missing documentation (doc comments, README, CONTRIBUTING, CHANGELOG, llms.txt). Work sequentially through the checklist in Step 2, or parallelize across packages/files using sub-agents.
Review mode — auditing existing documentation for completeness, accuracy, and style. Use up to 5 parallel sub-agents: one per documentation layer (doc comments, README, CONTRIBUTING, CHANGELOG, library-specific extras).