From go
Guidance for obtaining documentation in Go. Use when requiring documentation on Go entities e.g. packages, modules, types, functions, methods, etc.
npx claudepluginhub haleyrc/claude-plugins --plugin goThis skill uses the workspace's default tool permissions.
Use the `go doc` CLI for looking up documentation.
Verifies tests pass on completed feature branch, presents options to merge locally, create GitHub PR, keep as-is or discard; executes choice and cleans up worktree.
Guides root cause investigation for bugs, test failures, unexpected behavior, performance issues, and build failures before proposing fixes.
Writes implementation plans from specs for multi-step tasks, mapping files and breaking into TDD bite-sized steps before coding.
Share bugs, ideas, or general feedback.
Use the go doc CLI for looking up documentation.
For items in the standard library, you can reference packages and their contents directly:
go doc http # Returns documentation for the http package
go doc http.Server # Returns documentation for the Server type
go doc http.Server.Close # Returns documentation for the Close method
For third-party code, the package you are querying must already exist in go.mod or you will see a "cannot find package error". You must also include the full module path when calling go doc:
go doc github.com/google/uuid # Returns documentation for the uuid package
go doc github.com/google/uuid.UUID # Returns documentation for the UUID type
go doc github.com/google/uui.UUID.String # Returns documentation for the String method
For local code (code in the current project repository), you can either include the full module path or a relative path:
# Assuming we are in the `example` project:
go doc github.com/haleyrc/example/lib/log
go doc ./example/lib/log