go-dev

# Go Development Stack Opinionated, modern Go development setup. One tool per concern, zero overlap. ## When to Use - Starting a new Go project from scratch - Adding linting, formatting, or testing infrastructure - Setting up CI/CD for a Go service or library - Creating a Justfile to replace a Makefile - Adding database migration tooling - Migrating from scattered gofmt/govet/staticcheck invocations to a unified setup ## The Stack | Tool | Version | Role | Replaces | |------|---------|------|----------| | **Go** | 1.27+ | Language, toolchain, `go mod`, `go fix` | - | | **golangci-lint** | v2.13+ | Meta-linter (100+ linters + formatters + `fmt` command) | gofmt, govet, staticcheck, errcheck run separately | | **gofumpt** | v0.12+ | Strict formatter (superset of gofmt, 19 default rules) | gofmt | | **gotestsum** | v1.13+ | Test runner with readable output, watch mode, JUnit XML | Raw `go test` | | **just** | 1.58+ | Task runner | Makefile | | **golang-migrate** | v4.20+ | DB migrations (CLI + library + `embed.FS`) | Manual SQL scripts | | **lefthook** | v2.1+ | Git hooks (single binary, parallel) | pre-commit (Python) | **Version floors are load-bearing.** golangci-lint "supports Go versions lower or equal to the Go version used to compile it" - a pin older than your Go toolchain fails outright. Go 1.27 support landed in golangci-lint v2.13.0, so `v2.13` is the floor for a Go 1.27 project. Two more floors moved recently: gofumpt v0.12.0 "is based on Go 1.27's gofmt, and r...