Modernizing Go Codebases with the Revamped go fix Command

Introduction

With the release of Go 1.26, the go fix subcommand has been completely rebuilt to help developers modernize their codebases. This tool uses a collection of analysis algorithms to detect opportunities for improvement, often by leveraging newer language features or standard library functions. This article guides you through using go fix effectively, explores its internal architecture, and introduces the concept of self-service analysis for maintainers and organizations.

Using go fix

The go fix command works much like go build or go vet—it accepts package patterns. To fix all packages under the current directory, run:

$ go fix ./...

On success, the command silently updates your source files. If a generated file would be modified, the fix is discarded because the correct approach is to update the generator itself. It's recommended to run go fix over your project each time you update to a newer Go toolchain release. Starting from a clean git state ensures that your code reviewers see only the changes produced by go fix.

Previewing Changes

To see what changes would be applied without actually modifying your files, use the -diff flag:

$ go fix -diff ./...

This outputs a unified diff of the proposed edits. For example, it might transform:

- eq := strings.IndexByte(pair, '=')
- result[pair[:eq]] = pair[1+eq:]
+ before, after, _ := strings.Cut(pair, "=")
+ result[before] = after

Available Fixers

List all registered analyzers with:

$ go tool fix help

Currently the tool includes these fixers:

• any – replaces interface{} with any
• buildtag – checks //go:build and // +build directives
• fmtappendf – replaces []byte(fmt.Sprintf) with fmt.Appendf
• forvar – removes redundant re-declaration of loop variables (common before Go 1.22)
• hostport – checks address format passed to net.Dial
• inline – applies fixes based on //go:fix inline comment directives
• mapsloop – replaces explicit loops over maps with calls to the maps package
• minmax – replaces if/else statements with calls to min or max

For full documentation of a particular fixer, run go tool fix help <name>. For instance:

$ go tool fix help forvar

Understanding the Infrastructure

Behind the scenes, the revamped go fix is built on a new framework that allows analyzers to be easily added, composed, and configured. Each fixer is a static analysis pass that reports diagnostics and suggests replacements. The infrastructure supports not only automated fixes but also integration with go vet and other tools. This modular design enables the community to contribute new fixers and the Go team to rapidly ship improvements.

Self-Service Analysis

A key theme of the new go fix is self-service analysis. Module maintainers and organizations can encode their own guidelines and best practices into custom fixers. By leveraging the same analysis framework, teams can enforce internal coding standards, deprecate patterns, or encourage modern idioms. This empowers teams to scale their code quality efforts without relying solely on the core Go toolchain updates.