What problem does it solve? Releasing a multi-module Go monorepo is error-prone: every module needs its own semver git tag, the Go module proxy makes published versions immutable, and hand-rolled tagging produces broken pseudo-versions. This Skill walks maintainers through the complete two-phase gokit release process safely. ## Core Features & Use Cases - Pre-release gates: Runs the full build, vet, test, lint, vuln, and tidy checks via toven before any tag is cut. - Version decision support: Cross-checks the Go module proxy for every module path to pick a version strictly greater than anything already published. - Two-phase release: Stages the version bump and CHANGELOG rotation through a reviewed PR (Phase 1), then cuts lock-step module tags and the hosted GitHub Release via CI or toven release publish (Phase 2). - Use Case: Preparing gokit v0.3.0-alpha.1 — verify the proxy shows the version unpublished for all 50 modules, bump versions on a release branch, merge the PR, then dispatch the Release workflow with dry-run preview before publishing. ## Quick Start Ask the agent to prepare the gokit v0.3.0-alpha.1 release by running the pre-release gates and staging the version bump on a release branch.