Modernize Your Go Codebase with go fix: A Step-by-Step Guide

By • min read

Introduction

Go 1.26 introduced a completely rewritten go fix subcommand that goes beyond simple patching. It uses a suite of analyzers to identify opportunities to modernize your code—swapping interface{} for any, replacing manual loops with maps package calls, and much more. Running go fix regularly helps your codebase stay current with the latest language and library features, reducing technical debt and improving readability. This guide walks you through the entire process, from preparation to commit, so you can confidently modernize your Go project.

What You Need

• Go 1.26 or later – go fix is bundled with the toolchain. Verify with go version.
• A Go project – any module or package you want to modernize.
• Git (or another VCS) – to track changes and make reviewing easier.
• Basic command-line familiarity – you‘ll run commands in a terminal.
• No modifications in progress – start from a clean working tree to isolate go fix edits.

Step-by-Step Instructions

Step 1: Verify Your Go Version

First, confirm you’re running Go 1.26 or newer. Open a terminal and type:

go version

If the output shows a version earlier than 1.26, update your toolchain from the official download page. The rewritten go fix only ships with Go 1.26+.

Step 2: Prepare Your Workspace

Change into the root directory of your Go module:

cd /path/to/your/module

Ensure you have a clean git state so that any changes from go fix are easy to review. Run:

git status

If there are uncommitted changes, commit or stash them first. This step prevents accidental mixing of your edits with modernization fixes.

Step 3: Preview Changes with the -diff Flag

Before applying any fix, see what go fix would change. This gives you a chance to understand the impact. Run:

go fix -diff ./...

The ./... pattern means “all packages under the current directory.” The output shows unified diffs for each file that would be modified. For example, you might see a fix that replaces a manual string split with strings.Cut:

--- a/file.go
+++ b/file.go
@@ -1,5 +1,5 @@
-	eq := strings.IndexByte(pair, '=')
-	result[pair[:eq]] = pair[1+eq:]
+	before, after, _ := strings.Cut(pair, "=")
+	result[before] = after

Review the diff. If any changes look wrong, you can skip the whole fix or use specific analyzers (see Step 5).

Step 4: Apply the Fixes

Once you’ve previewed and are satisfied, run the actual fix command:

go fix ./...

This silently updates your source files. Generated files (e.g., from stringer) are skipped because the fix should be applied to the generator itself. After the command finishes, check git diff to see all modified files:

git diff --stat

You can then commit the changes with a descriptive message, e.g., "all: run go fix to modernize codebase".

Step 5: Explore and Run Specific Analyzers

If you only want to apply a subset of fixes, or you want to understand what each analyzer does, list the available fixers:

go tool fix help

You’ll see output like:

Registered analyzers:
    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
    hostport     check format of addresses passed to net.Dial
    inline       apply fixes based on 'go:fix inline' comment directives
    mapsloop     replace explicit loops over maps with calls to maps package
    minmax       replace if/else statements with calls to min or max
    …

To see documentation for a specific analyzer, use go tool fix help <name>. For example:

go tool fix help any

To run only certain fixers, use the -fix flag with a comma-separated list. For instance:

go fix -fix=any,minmax ./...

This restricts go fix to just the any and minmax analyzers. You can also exclude analyzers with -fix=-foo (prefix minus sign).

Step 6: Integrate into Your Workflow

Make go fix part of your regular update process. Whenever you upgrade your Go toolchain, run go fix first. This ensures your code takes advantage of new language features and library improvements immediately. Consider adding a git hook or a CI step that runs go fix -diff (but not the actual write) to flag opportunities for modernization. However, remember to apply fixes manually after reviewing.

Tips & Conclusion

• Always preview first. The -diff flag is your friend. It prevents surprises and helps you understand what changed.
• Start from a clean state. Commit or stash your work before running go fix so the diff shows only modernization edits.
• Run after each Go release. New analyzers are added over time. Running go fix with a newer toolchain may apply additional beneficial changes.
• Use specific analyzers for targeted upgrades. If you’re not ready to apply all fixes, pick the ones that align with your project’s timeline.
• Review generator fixes separately. If go fix skips generated files, it’s because the fix should be in the generator itself. Update your code generation tools appropriately.
• Keep your team informed. When you commit go fix changes, mention which analyzers were applied to help reviewers understand the scope.

Modernizing your Go code doesn’t have to be a manual, error-prone task. With go fix, you can apply a suite of proven transformations in seconds, keeping your codebase fresh and idiomatic. Start with a preview, apply the fixes you need, and make it a routine part of your development cycle. Your future self—and your code reviewers—will thank you.