New 'go fix' Overhauls Codebase Upgrades
The Go programming language’s 1.26 release, shipping this month, introduces a completely rewritten go fix subcommand that automatically identifies and applies modern language and library improvements. The update promises to save developers hours of manual refactoring across large projects.
According to Alan Donovan, a key contributor to the Go team at Google, “The new go fix uses a suite of algorithms to detect outdated patterns and replace them with current best practices—all with zero configuration.” He emphasized that the tool is designed to be run after each toolchain upgrade. “Start from a clean git state so your change history is clean and reviews are straightforward,” Donovan added.
Background: Why a Rewrite Was Needed
The original go fix was introduced early in Go’s history to handle simple, hard‑coded transformations. Over time, the language evolved faster than the tool could keep up. The Go 1.22 loop variable change, for instance, required manual code updates because the old fixer couldn’t handle the new semantics.
The 1.26 rewrite transforms the subcommand into a modular analysis framework. Each “fixer” is a standalone analyzer that can be enabled, disabled, or extended. The team also added support for //go:fix inline directives, letting library authors ship their own automated migration suggestions.
How It Works: Running and Previewing Fixes
Developers can run go fix ./... to apply all relevant fixes to the current package tree. The command silently modifies source files but skips generated code—leaving those fixes to the generator’s logic. To preview changes without applying them, use the -diff flag:
$ go fix -diff ./...
The output shows old and new code side by side, so you can verify every change before committing.
To see all available fixers, type go tool fix help. The current list includes analyzers for replacing interface{} with any, converting []byte(fmt.Sprintf) to fmt.Appendf, removing redundant loop‑variable shadowing (the forvar fixer), and more.
What This Means for Developers
For individual programmers, go fix eliminates tedious, error‑prone manual updates. Teams adopting new Go releases can modernize entire codebases in seconds. The tool’s modular architecture also paves the way for third‑party analyzers, allowing organizations to encode their own coding standards as automated fixers.
Donovan described the shift as “self‑service analysis. Instead of waiting for a new Go release to fix old patterns, maintainers can write custom analyzers that match their domain.” This empowers companies to gradually migrate legacy code while keeping pace with the language’s evolution.
Who Should Act
All Go developers are encouraged to run go fix ./... after upgrading to Go 1.26. Those maintaining public modules should also consider adding //go:fix inline migration hints to help downstream users. The Go team plans to expand the built‑in fixer set in future releases, making the tool an essential part of every Go workflow.