go-documentation

Identify missing or weak godoc for exported Go APIs and examples.

8|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/muratmirgun/gophers --skill go-documentation-muratmirgun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-documentation
Source: https://github.com/muratmirgun/gophers/tree/main/skills/go-documentation
Command: npx skills add https://github.com/muratmirgun/gophers --skill go-documentation-muratmirgun

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you write and review Go documentation that actually improves API usability, rather than repeating code signatures or leaving exported symbols undocumented.

Core Features & Use Cases

  • Godoc Coverage: Ensures every exported package member has a proper comment, including packages, types, functions, methods, constants, variables, and sentinel errors.
  • Readable Examples: Guides you in creating runnable Example tests with verified output so documentation stays accurate and executable.
  • Project-Aware Docs: Adapts documentation guidance based on whether the repository is a library, CLI application, or both, including README, CONTRIBUTING, and CHANGELOG expectations.
  • Use Case: You add a new exported Go type and want the documentation to follow Go conventions, include the right package-level comment, and present a minimal runnable example.

Quick Start

Ask the skill to review your Go package documentation and tell you which exported names, examples, and README sections need to be added or fixed.

Frequently Asked Questions about go-documentation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ensure my Go exported APIs have proper godoc comments?

To ensure proper godoc comments for Go exported APIs, review exported packages, types, functions, methods, constants, variables, and sentinel errors to verify each has a proper comment following Go conventions. This documentation coverage aligns with Go tooling requirements verified by go doc.

What is the best way to write runnable Example tests for a Go package?

The best way to write runnable Example tests for a Go package is to create verified output examples that stay accurate and executable. This ensures your documentation presents minimal runnable examples that pass documentation structure verification via go test.

How do I structure README and project documentation for a Go CLI application?

Structuring README and project documentation for a Go CLI application requires adapting guidance based on whether the repository is a library, CLI, or both. This includes establishing README, CONTRIBUTING, and CHANGELOG expectations that align with Go project conventions.

Does Go documentation tooling require package-level comments for exported types?

Go documentation tooling does require package-level comments for exported types to ensure API usability. Proper package summaries and exported symbol comments must be included to satisfy documentation coverage requirements verified by go doc and go test commands.

Why does my Go documentation fail to generate properly for exported symbols?

Go documentation fails to generate properly when exported symbols lack proper comments or contain weak godoc. Missing package comments, undocumented exported APIs, or absent deprecation markers prevent proper documentation structure verification by go doc.