go/modules

Manage Go modules, versions, and workspaces for reproducible builds.

3|1|Updated Feb 10, 2026

Search Tags:#versioning #security #go #modules #workspaces #vendoring #replace-directive

Ready to run

npx skills add https://github.com/deandum/claude-resources --skill go-modules-deandum

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: go/modules
Source: https://github.com/deandum/claude-resources/tree/main/skills/go/modules
Command: npx skills add https://github.com/deandum/claude-resources --skill go-modules-deandum

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Go module management for Go projects, including handling go.mod/go.sum, versioning strategies, replace directives, vendoring, and workspace coordination to ensure reproducible builds.

Core Features & Use Cases

Versioning and v2+ suffix guidance for module paths and imports.
Replace and vendoring strategies for local development and hermetic releases.
Workspace mode with go.work to coordinate multiple modules in monorepos.
Security and CI validation using govulncheck and tidy checks for production readiness.
Use Case: A large Go monorepo with multiple internal modules benefits from a shared module graph and pinned versions.

Quick Start

Set up your Go project to use modules, initialize a workspace with go work, and run tidy to ensure reproducible builds.

Frequently Asked Questions about go/modules

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

FAQPage Schema

How do I manage Go modules to ensure reproducible builds?▼

To ensure reproducible builds with Go modules, you must manage go.mod and go.sum files, enforce tidy correctness, and pin module versions. This approach guarantees consistent dependency resolution across different environments.

What is the best way to coordinate multiple Go modules in a monorepo?▼

The best way to coordinate multiple Go modules in a monorepo is using workspace mode with go.work. This establishes a shared module graph to synchronize dependencies and pinned versions across the modules.

How do I use replace directives for local development in Go?▼

Replace directives in Go redirect module paths to local copies or specific versions for local development and hermetic releases. This allows you to test unpublished changes without modifying the upstream module graph.

When do I need v2+ suffixes for Go module paths and imports?▼

You need v2+ suffixes for Go module paths and imports when a module reaches major version 2 or higher. This versioning strategy ensures import paths remain unique and prevent breaking changes in downstream dependencies.

Does Go module management support vulnerability scanning in CI?▼

Yes, Go module management supports vulnerability scanning in CI by integrating govulncheck. This validates production readiness by detecting known vulnerabilities in your module dependencies during the build process.

How do I use vendoring for hermetic releases in Go projects?▼

Vendoring for hermetic releases in Go projects involves storing dependencies locally within the repository to guarantee availability. This strategy ensures builds remain reproducible without relying on external module proxies.