Go rewards small, stable public APIs — but READMEs and usage guides still fall behind as you refactor internals and adjust exported signatures. docs-keeper parses your Go with Tree-sitter and keeps the human docs aligned with the exported surface.
Package docs that match your exported API
docs-keeper reads your packages, structs, and exported functions and rewrites the docs when the public API changes.
What docs-keeper keeps in sync
Package overview
Exported types, functions, and interfaces documented from their real signatures.
Usage examples
README snippets updated when exported APIs change.
CLI flags
Command-line flags and subcommands documented as they evolve.
Versioned changes
Breaking changes to the public API surfaced in drafted changelog entries.
Docs it writes for Go
README.mdPackage docsCLI referenceCHANGELOG.mdExamples
Frequently asked
How is this different from godoc?
godoc renders your doc comments. docs-keeper writes and maintains the surrounding prose — READMEs, guides, examples — and grounds it in the same exported API.
Does it respect exported vs unexported?
Drafts focus on the public surface; unexported internals inform context but aren’t the subject of user-facing docs.
Modules and workspaces?
You choose which module paths to include, so multi-module repos only get docs where you want them.
Try docs-keeper on your Go repo
One public repo, 20 doc PRs per month, no credit card. See if drafts read like your team before committing to a paid plan.