gotools

package module

v0.6.7 Latest Latest Go to latest Published: Aug 15, 2026 License: MIT Imports: 1 Imported by: 0

Details

Valid go.mod file
Redistributable license
Tagged version
Stable version
Learn more about best practices

Repository

github.com/piusalfred/gotools

Links

Open Source Insights

README ¶

gotools.sh

A wrapper around go get -tool with added ergonomics like dependency isolation, deterministic sync, managed execution, and CI-friendly diagnostics.

But why?

Installing tools straight into your project's go.mod pollutes the dependency graph with tool-only dependencies. gotools.sh keeps tool dependencies isolated behind three strategies. See Strategies for more details.

⚠️ Tools are compiled locally from source (go get -tool) — read the risks and recommendations before committing to a strategy.

Requirements

Go 1.24 or higher

Install

go install github.com/piusalfred/gotools/cmd/gotools@latest

For more installation options, See Installation options.

Quick Start

# Bootstrap with the default split strategy
gotools init

# Install some tools
gotools install github.com/google/addlicense
gotools install golangci-lint \
  github.com/golangci/golangci-lint/v2/cmd/golangci-lint@v2.11.4

# Run a tool
gotools exec addlicense -l mit -c "Your Name" .
gotools exec golangci-lint run ./...

# List all managed tools
gotools list

Run gotools help for the full command reference. You can also check out the USAGE documentation for more examples and details.

Features


Three Isolation Strategies	Choose between `split` (default), `module` (safest), or `unified` (simplest).
Go Version Parity	Tool environments automatically sync to the Go version defined in your project's root `go.mod`.
Seamless Migration	Move between strategies dynamically with the `migrate` command without losing your pinned versions.
Auto-Migration on Sync	If the tools directory structure doesn't match `.gotools.json`, `sync` detects the mismatch and migrates automatically.
Reproducibility	Commit the `tools/` directory to guarantee environment parity across teams and CI.
Self-Update	Update `gotools.sh` itself with a single command.

Documentation

Doc	Contents
USAGE	Command reference, examples, risks, doctor, JSON output, shell completions, cleanup, exit codes
INSTALLATION	All installation methods: pre-built binaries, curl installer, vendored script, version pinning
STRATEGIES	The three isolation strategies compared
MIGRATION	Moving between strategies
CONFIGURATION	The `.gotools.json` manifest, schema versioning, module prefix
CI	CI integration, version guard, offline mode, locking and timeouts, pre-commit
DEVELOPMENT	Source layout, building, testing, releases (for contributors)