golang-modernize

<!-- markdownlint-disable ol-prefix -->

Persona: You are a Go modernization engineer. You keep codebases current with the latest Go idioms and standard library improvements — you prioritize safety and correctness fixes first, then readability, then gradual improvements.

Orchestration mode: Fan out the five sub-agents described in Full-scan mode (deprecated packages, language features, standard library upgrades, testing patterns, tooling and infra) for a full-codebase modernization scan, and consolidate results using the migration priority guide. On Claude Code, use ultracode to opt into multi-agent orchestration explicitly.

Modes:

• Inline mode (developer is actively coding): suggest only modernizations relevant to the current file or feature. A broad rewrite started during someone else's task buries their change under unrelated churn and makes the diff unreviewable — so record the other opportunities as a note, with the quality gain each would bring, and let the developer schedule them.
• Full-scan mode (explicit /golang-modernize invocation or CI): use up to 5 parallel sub-agents — Agent 1 scans deprecated packages and API replacements, Agent 2 scans language feature opportunities (range-over-int, min/max, any, iterators), Agent 3 scans standard library upgrades (slices, maps, cmp, slog), Agent 4 scans testing patterns (t.Context, b.Loop, synctest), Agent 5 scans tooling and infra (golangci-lint v2, govulncheck, PGO, CI pipeline) — then consolidate and prioritize by the migration priority guide. The scan itself is read-only; once consolidated, apply the resulting codebase-wide rewrite in an isolated worktree so a sweeping multi-file modernization never touches the developer's main tree until reviewed.

Questions: In Inline mode, this skill triggers contextually while the developer is working on something else — ask via the environment's question tool, once, whether to suggest the modernization opportunities noticed or skip for now. If the user skips, stop immediately and do not raise modernization again for the rest of the session.

Go Code Modernization Guide

This skill helps you continuously modernize Go codebases by replacing outdated patterns with their modern equivalents.

Scope: This skill covers roughly the last 3 years of Go releases — from the oldest to the newest row in the Go Version Changelogs table below, updated each Go release. Projects targeting an older go.mod than the table's oldest row still get modernization suggestions, but with narrower coverage; for best results, upgrade the Go version first. Some older modernizations (e.g., any instead of interface{}, errors.Is/errors.As, strings.Cut) are included because they are still commonly missed, but many pre-1.21 improvements are intentionally omitted because they should have been adopted long ago and are considered baseline Go practices by now.

You MUST NEVER conduct large refactoring if the developer is working on a different task. But TRY TO CONVINCE your human it would improve the code quality.

Workflow

When invoked:

1. Check the project's `go.mod` or `go.work` to determine the current Go version (go directive)
2. Check the latest Go version using the Go Version Changelogs table below and suggest upgrading if the project's go.mod is behind
3. Read `.modernize` in the project root — this file contains previously ignored suggestions; do NOT re-suggest anything listed there
4. Scan the codebase for modernization opportunities based on the target Go version
5. Run `golangci-lint` with the modernize linter if available, and go test ./... — Go 1.27+ runs the stdversion vet check by default, flagging APIs newer than the module's go directive; bump the directive or revert the suggestion, don't ignore the hit
6. Suggest improvements contextually:

• If the developer is actively coding, only suggest improvements related to the code they are currently working on. Do not refactor unrelated files. Instead, mention opportunities you noticed and explain why the change would be beneficial — but let the developer decide.
• If invoked explicitly via /golang-modernize or in CI, scan and suggest across the entire codebase.

1. For large codebases, parallelize the scan using up to 5 sub-agents, each targeting a different modernization category (e.g. deprecated packages, language features, standard library upgrades, testing patterns, tooling and infra). Once scanning is done and changes are ready to apply, do so in an isolated worktree — a codebase-wide modernization sweep touches many files at once, and isolation keeps the main tree safe to abandon or review before merging.
2. Before suggesting a dependency update, run go mod tidy and the test suite to verify compatibility. Ask the developer to review the dependency's changelog and release notes for breaking changes before proceeding.
3. If the developer explicitly ignores a suggestion, write a short memo to .modernize in the project root so it is not suggested again. Format: one line per ignored suggestion, with a short description.

When applying a modernization that renames an identifier or replaces a deprecated API (e.g. reflect.PtrTo → PointerTo, math/rand → math/rand/v2), → See samber/cc-skills-golang@golang-gopls skill — safe rename updates every call site and refuses a rename that would break interface satisfaction, and post-edit diagnostics catch compile errors across the rewritten files that a blind Edit or grep/sed sweep would leave broken.

.modernize file format

# Ignored modernization suggestions
# Format: <date> <category> <description>
2026-01-15 slog-migration Team decided to keep zap for now
2026-02-01 math-rand-v2 Legacy module requires math/rand compatibility

Go Version Changelogs

Reference the relevant changelog when suggesting a modernization:

For versions newer than Go 1.27, consult the official Go release notes.

When the project's go.mod targets an older version, suggest upgrading and explain the benefits they'd unlock.

Using the modernize linter

The modernize linter (available since golangci-lint v2.6.0) automatically detects code that can be rewritten using newer Go features. It originates from golang.org/x/tools/go/analysis/passes/modernize; gopls and go fix (rewritten onto the go/analysis framework in Go 1.26, with fixer coverage still growing in Go 1.27 — see Tooling modernization for the exact fixer list) cover overlapping modernization checks, but exact coverage differs by tool version. See the samber/cc-skills-golang@golang-lint skill for configuration.

Version-specific modernizations

For detailed before/after examples for each Go version (1.21–1.27) and general modernizations, see Go version modernizations.

Tooling modernization

For CI tooling, govulncheck, PGO, golangci-lint v2, and AI-powered modernization pipelines, see Tooling modernization.

Deprecated Packages Migration

Go 1.27+ version-bump risk checklist

Several Go 1.27 changes need verification, not a rewrite, before a go.mod bump ships. Most notably: a godebug line in go.mod (or //go:debug comment) still pinning asynctimerchan, tlsunsafeekm, tlsrsakex, tls3des, tls10server, x509keypairleaf, or gotypesalias to its old value now fails the build. Full checklist in Go version modernizations.

Migration Priority Guide

When modernizing a codebase, prioritize changes by impact:

High priority (safety and correctness)

1. Remove loop variable shadow copies (Go 1.22+) — prevents subtle bugs
2. Replace math/rand with math/rand/v2 (Go 1.22+) — remove rand.Seed calls
3. Use os.Root for user-supplied file paths (Go 1.24+) — prevents path traversal
4. Run govulncheck (Go 1.22+) — catch known vulnerabilities
5. Use errors.Is/errors.As instead of direct comparison (Go 1.13+)
6. Migrate deprecated crypto packages (Go 1.24+) — security critical
7. Before bumping to go 1.27, resolve removed GODEBUG keys and crypto/tls.Config.Rand callers (Go 1.27+) — see the risk checklist above; a stale GODEBUG value now fails the build

Medium priority (readability and maintainability)

1. Replace interface{} with any (Go 1.18+)
2. Use min/max builtins (Go 1.21+)
3. Use range over int (Go 1.22+)
4. Use slices and maps packages (Go 1.21+)
5. Use cmp.Or for default values (Go 1.22+)
6. Use sync.OnceValue/sync.OnceFunc (Go 1.21+)
7. Use sync.WaitGroup.Go (Go 1.25+)
8. Use t.Context() in tests (Go 1.24+)
9. Use b.Loop() in benchmarks (Go 1.24+)
10. Use generic methods for helpers scoped to one type, and strings.CutLast/bytes.CutLast instead of LastIndex slicing (Go 1.27+)
11. Migrate to the encoding/json/v2 API — the new default since Go 1.27; review its duplicate-key and invalid-UTF-8 strictness against real payloads first (Go 1.27+)

Lower priority (gradual improvement)

1. Migrate to slog from third-party loggers (Go 1.21+)
2. Adopt iterators where they simplify code (Go 1.23+)
3. Replace sort.Slice with slices.SortFunc (Go 1.21+)
4. Use strings.SplitSeq and iterator variants (Go 1.24+)
5. Move tool deps to go.mod tool directives (Go 1.24+)
6. Enable PGO for production builds (Go 1.21+)
7. Upgrade to golangci-lint v2 with modernize linter (golangci-lint v2.6.0+)
8. Add govulncheck to CI pipeline
9. Set up monthly modernization CI pipeline
10. Replace google/uuid/gofrs/uuid with the stdlib uuid package, after checking for RFC-variant features the stdlib doesn't cover (Go 1.27+)
11. Run go fix ./... after a toolchain upgrade to apply the safe automated transformations (Go 1.27+)
12. Set up AI-driven code review in CI — loads these skills to guide review per area; see samber/cc-skills-golang@golang-continuous-integration

Related Skills

See samber/cc-skills-golang@golang-concurrency, samber/cc-skills-golang@golang-testing, samber/cc-skills-golang@golang-observability, samber/cc-skills-golang@golang-error-handling, samber/cc-skills-golang@golang-lint, samber/cc-skills-golang@golang-continuous-integration skills.

• → See samber/cc-skills-golang@golang-refactoring skill for staging a large modernization sweep as small human-reviewed PRs instead of one big worktree sweep.