Go Version Manager

Choose the project-compatible Go toolchain before changing dependencies. Prefer the machine's existing goenv installation for real version switching. Fall back to explicit binary paths when no supported version manager is available.

Workflow

1. Read go.mod completely enough to identify go, toolchain, and replace directives.
2. Run .agents/skills/go-version-manager/scripts/go-version-manager.sh requirement <project-dir>, manager, and list.
3. Run .agents/skills/go-version-manager/scripts/go-version-manager.sh select <project-dir> to choose an installed binary.
4. Confirm the selected binary with <go-binary> version and <go-binary> env GOROOT GOTOOLCHAIN GOPATH GOMODCACHE GOCACHE.
5. Choose the switching scope:
   • For one command, use the script's exec command. With goenv, it sets GOENV_VERSION only for that command.
   • For the current terminal, run the command printed by shell-command (normally goenv shell <version>).
   • For a repository-persistent selection, use switch-local; this runs goenv local <version> and writes .go-version, so do it only when the user authorizes a repository change.
   • Change goenv global only when the user explicitly requests a machine-wide default change.
6. Review git diff -- go.mod go.sum after any module command.
7. Report the selected version, commands run, dependency changes, and verification result.

Selection rules