Go 1.26 Overhauls 'go fix' for Automated Code Modernization

Go 1.26 Delivers a Ground-Up Rewrite of the go fix Command

In a move that will save thousands of developer hours, the Go 1.26 release, launched this month, includes a completely rewritten go fix subcommand. The new tool uses a suite of analysis algorithms to automatically identify and apply code improvements, often by leveraging modern language and library features.

“Running go fix over your project each time you update your build to a newer Go toolchain release is recommended,” said Alan Donovan, a Go team member. “Since the command may fix hundreds of files, start from a clean git state so that the change consists only of edits from go fix; your code reviewers will thank you.”

Running go fix

Like go build and go vet, go fix accepts package patterns. To fix all packages beneath the current directory, simply run:

$ go fix ./...

On success, source files are silently updated. The tool skips generated files, as the appropriate fix in that case lies in the generator logic itself. To preview changes, use the -diff flag:

$ go fix -diff ./...

This shows a unified diff, such as replacing manual strings.IndexByte logic with the cleaner strings.Cut call.

Available Fixers and Their Documentation

You can list all registered fixers with go tool fix help. The current set includes:

• 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
• hostport – checks address formats passed to net.Dial
• inline – applies fixes based on //go:fix inline comment directives
• mapsloop – replaces explicit loops over maps with maps package calls
• minmax – replaces if/else with calls to min or max

Detailed help for a specific analyzer, like forvar, explains its purpose: “The forvar analyzer removes unnecessary shadowing of loop variables. Before Go 1.22, it was common to re-declare loop variables, which is now redundant.”

Background: The Evolution of go fix

The original go fix was introduced early in Go’s history to automate mechanical transformations, such as updating API usage after language changes. Over time, it became a critical tool for large-scale migrations. However, its architecture was aging and limited in scope.

Go 1.26’s rewrite modernizes the underlying infrastructure, enabling a broader set of analysis-driven improvements. The new system is designed to be extensible, allowing the community to contribute self-service analyzers. “We’re presenting a theme of self-service analysis tools to help module maintainers and organizations encode their own guidelines and best practices,” the Go team explains.

What This Means for Developers

For individual developers, the new go fix reduces manual code reviews and accelerates adoption of idiomatic patterns. Team leads can enforce consistent coding standards without micromanaging. The tool’s ability to handle hundreds of files in a single pass makes it practical to run as part of continuous integration pipelines.

Organizations that maintain large Go monorepos will particularly benefit. The go fix command can be used to enforce custom policies via future self-service analyzers, turning code modernization into an automated, low-risk process. “Start from a clean git state,” reminds Donovan, ensuring that each run produces a clean diff for review.

Longer term, this rewrite lays the groundwork for deeper static analysis integration within the Go toolchain. As the ecosystem grows, go fix will likely become an indispensable part of every Go developer’s workflow—not just for migration, but for continuous code health.