Modernizing Go Codebases with the Revamped `go fix` Command

Introduction

The Go ecosystem constantly evolves, introducing new language features, standard library improvements, and best practices. Keeping your codebase aligned with modern Go can be a daunting task, especially in large projects. The go fix command, recently rewritten for Go 1.26, automates this process. It uses a suite of static analyzers to identify and apply improvements, from replacing interface{} with any to simplifying loops with the maps package. This article walks you through using go fix effectively, explores its underlying architecture, and highlights how it can be extended for team-specific guidelines.

Getting Started with go fix

Like go build and go vet, go fix accepts package patterns. To fix all packages in your project, run:

$ go fix ./...

On success, the command silently updates your source files. If a file is generated, the fix is skipped because the generator itself should be corrected instead. We recommend running go fix every time you upgrade your Go toolchain. Start from a clean git state, so your commit contains only the fixer’s changes—your code reviewers will appreciate it.

Previewing Changes with -diff

Curious what go fix would do? Use the -diff flag to see a unified diff without modifying any files:

$ go fix -diff ./...

This shows before-and-after snippets, like replacing strings.IndexByte and manual substring extraction with a simpler strings.Cut call. The diff helps you understand each transformation before committing.

Exploring Available Fixes

List all registered analyzers with:

$ go tool fix help

This prints a list of fixers such as:

• any – replace interface{} with any
• buildtag – check //go:build and // +build directives
• fmtappendf – replace []byte(fmt.Sprintf) with fmt.Appendf
• forvar – remove redundant re-declaration of loop variables (common before Go 1.22)
• hostport – validate address formats passed to net.Dial
• inline – apply fixes based on //go:fix inline comments
• mapsloop – replace explicit map loops with maps package calls
• minmax – replace if/else with min or max

To see detailed documentation for a specific analyzer, add its name:

$ go tool fix help forvar

The Infrastructure Behind go fix

The rewritten go fix is built on top of the Go analysis framework, similar to go vet. Each fixer is a modular analyzer that can detect outdated patterns and suggest replacements. The framework handles file reading, parsing, and writing, so analyzer authors focus on logic. This modular design allows the Go team to add new fixers quickly and allows third parties to create custom analyzers. The go fix infrastructure also respects //go:generate directives and skips generated files, preventing accidental overwrites of auto‑generated code.

Self-Service Analysis and Custom Rules

Beyond the built‑in fixes, the Go team encourages the community to build their own static analysis tools. The same infrastructure that powers go fix can be extended to encode organization‑wide best practices. For instance, a company might create an analyzer that enforces specific logging conventions or deprecates internal APIs. The go fix command will eventually support pluggable analyzers, making it a self‑service platform for code modernization.

This theme of self‑service analysis empowers module maintainers to define and enforce their own guidelines, reducing the burden of manual code reviews. As the Go ecosystem grows, the ability to automatically upgrade code becomes indispensable—go fix is the tool that makes ongoing modernization practical.