golang-modernize
Skill0 starsChanged 2 months agoMITView on GitHub
Modernize Golang code to use recent language features, standard library improvements, and idiomatic patterns. Use when reviewing Go code with old-style patterns, when encountering a deprecation warning, or when the user asks for modernization, a Go version upgrade (e.g. to Go 1.27), or a CI/tooling refresh. Not for structural refactors, extracting functions, or moving code between packages (→ See `samber/cc-skills-golang@golang-refactoring` skill).
- Installs packages
12 other projects use a version of this, 9 of them edited.
Adopted by
Most recently taken up by
- aiproxer/aiproxertheir own version, first seen Nov 8, 2026
- TeddyAlbina/skillsedited, first seen Nov 1, 2026
- samber/cc-skills-golangword for word, first seen Nov 1, 2026
- poizoncoded/skillsedited, first seen Nov 1, 2026
- klawisha012/agentsyncedited, first seen Oct 25, 2026
- jniltinho/llama-modeledited, first seen Oct 15, 2026
Other versions12 projects use a version of this.
Word for word · 1
- samber/cc-skills-golang★ 3.9k100% same
Edited · 9
- alexastrum/skl★ 1175% same
- klawisha012/agentsync★ 1077% same
- tstapler/dotfiles★ 8100% same
- poizoncoded/skills★ 271% same
- TeddyAlbina/skills★ 275% same
- rockcookies/skills★ 182% same
- VerifiedOrganic/onboard★ 175% same
- guynhsichngeodiec/cc-skills-golang★ 074% same
- jniltinho/llama-model★ 075% same
Wrote their own version · 2
- aiproxer/aiproxer★ 24same name
- reagin/agent-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository45 other files it gives its agents.
- golang-benchmarkSkill
- golang-cliSkill
- golang-code-styleSkill
- golang-concurrencySkill
- golang-contextSkill
- golang-continuous-integrationSkill
- golang-databaseSkill
- golang-data-structuresSkill
- golang-dependency-injectionSkill
- golang-dependency-managementSkill
- golang-design-patternsSkill
- golang-documentationSkill
- golang-error-handlingSkill
- golang-google-wireSkill
- golang-goplsSkill
- golang-graphqlSkill
- golang-grpcSkill
- golang-how-toSkill
- golang-lintSkill
- golang-namingSkill
- golang-observabilitySkill
- golang-performanceSkill
- golang-pkg-go-devSkill
- golang-popular-librariesSkill
- golang-project-layoutSkill
- golang-refactoringSkill
- golang-safetySkill
- golang-samber-doSkill
- golang-samber-hotSkill
- golang-samber-loSkill
- golang-samber-moSkill
- golang-samber-oopsSkill
- golang-samber-roSkill
- golang-samber-slogSkill
- golang-securitySkill
- golang-spf13-cobraSkill
- golang-spf13-viperSkill
- golang-stay-updatedSkill
- golang-stretchr-testifySkill
- golang-structs-interfacesSkill
- golang-swaggerSkill
- golang-testingSkill
- golang-troubleshootingSkill
- golang-uber-digSkill
- golang-uber-fxSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. 3 are common, 0 are distinctive, and 17 are very specific to this project.
3
Common
Most of the 11 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
17
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 54
If the developer is actively coding, only suggest improvements related to the code they are currently working on.
- Very specific: line 55
If invoked explicitly via /golang-modernize or in CI, scan and suggest across the entire codebase.
- Very specific: line 87
When the project's go.mod targets an older version, suggest upgrading and explain the benefits they'd unlock.
- Common: line 127
When modernizing a codebase, prioritize changes by impact:
- Common: line 131
Remove loop variable shadow copies _(Go 1.22+)_ — prevents subtle bugs
- Very specific: line 133
Use os.Root for user-supplied file paths _(Go 1.24+)_ — prevents path traversal
- Very specific: line 134
Run govulncheck _(Go 1.22+)_ — catch known vulnerabilities
- Very specific: line 135
Use errors.Is/errors.As instead of direct comparison _(Go 1.13+)_
- Very specific: line 137
Before bumping to go 1.27, resolve removed GODEBUG keys and crypto/tls.Config.Rand callers _(Go 1.27+)_ — see the risk checklist above.
- Very specific: line 142
Use min/max builtins _(Go 1.21+)_
- Very specific: line 143
Use range over int _(Go 1.22+)_
- Very specific: line 144
Use slices and maps packages _(Go 1.21+)_
- Very specific: line 145
Use cmp.Or for default values _(Go 1.22+)_
- Very specific: line 146
Use sync.OnceValue/sync.OnceFunc _(Go 1.21+)_
- Very specific: line 148
Use t.Context() in tests _(Go 1.24+)_
- Very specific: line 149
Use b.Loop() in benchmarks _(Go 1.24+)_
- Very specific: line 150
Use generic methods for helpers scoped to one type, and strings.CutLast/bytes.CutLast instead of LastIndex slicing _(Go 1.27+)_
- Very specific: line 158
Use strings.SplitSeq and iterator variants _(Go 1.24+)_
- Very specific: line 162
Add govulncheck to CI pipeline
- Very specific: line 165
Run go fix ./... after a toolchain upgrade to apply the safe automated transformations _(Go 1.27+)_
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- 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-modernizeinvocation 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:
- Check the project's
go.modorgo.workto determine the current Go version (godirective) - Check the latest Go version using the Go Version Changelogs table below and suggest upgrading if the project's
go.modis behind - Read
.modernizein the project root — this file contains previously ignored suggestions; do NOT re-suggest anything listed there - Scan the codebase for modernization opportunities based on the target Go version
- Run
golangci-lintwith themodernizelinter if available, andgo test ./...— Go 1.27+ runs thestdversionvet check by default, flagging APIs newer than the module'sgodirective; bump the directive or revert the suggestion, don't ignore the hit - 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-modernizeor in CI, scan and suggest across the entire codebase.
- 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.
- Before suggesting a dependency update, run
go mod tidyand the test suite to verify compatibility. Ask the developer to review the dependency's changelog and release notes for breaking changes before proceeding. - If the developer explicitly ignores a suggestion, write a short memo to
.modernizein 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 compatibilityGo Version Changelogs
Reference the relevant changelog when suggesting a modernization:
| Version | Release | Changelog |
| Go 1.21 | August 2023 | https://go.dev/doc/go1.21 |
| Go 1.22 | February 2024 | https://go.dev/doc/go1.22 |
| Go 1.23 | August 2024 | https://go.dev/doc/go1.23 |
| Go 1.24 | February 2025 | https://go.dev/doc/go1.24 |
| Go 1.25 | August 2025 | https://go.dev/doc/go1.25 |
| Go 1.26 | February 2026 | https://go.dev/doc/go1.26 |
| Go 1.27 | August 2026 | https://go.dev/doc/go1.27 |
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
| Deprecated | Replacement | Since |
math/rand | math/rand/v2 | Go 1.22 |
crypto/elliptic (most functions) | crypto/ecdh | Go 1.21 |
reflect.SliceHeader, StringHeader | unsafe.Slice, unsafe.String | Go 1.21 |
reflect.PtrTo | reflect.PointerTo | Go 1.22 |
runtime.GOROOT() | go env GOROOT | Go 1.24 |
runtime.SetFinalizer | runtime.AddCleanup | Go 1.24 |
crypto/cipher.NewOFB, NewCFB* | AEAD modes or NewCTR | Go 1.24 |
golang.org/x/crypto/sha3 | crypto/sha3 | Go 1.24 |
golang.org/x/crypto/hkdf | crypto/hkdf | Go 1.24 |
golang.org/x/crypto/pbkdf2 | crypto/pbkdf2 | Go 1.24 |
testing/synctest.Run | testing/synctest.Test | Go 1.25 |
crypto/rsa.EncryptPKCS1v15 for new encryption use | RSA-OAEP (rsa.EncryptOAEP / rsa.EncryptOAEPWithOptions) or HPKE/KEM design | Go 1.26 |
net/http/httputil.ReverseProxy.Director | ReverseProxy.Rewrite | Go 1.26 |
crypto/tls.Config.Rand | testing/cryptotest.SetGlobalRandom() | Go 1.27 |
github.com/google/uuid (simple cases) | uuid (stdlib) | Go 1.27 |
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)
- Remove loop variable shadow copies (Go 1.22+) — prevents subtle bugs
- Replace
math/randwithmath/rand/v2(Go 1.22+) — removerand.Seedcalls - Use
os.Rootfor user-supplied file paths (Go 1.24+) — prevents path traversal - Run
govulncheck(Go 1.22+) — catch known vulnerabilities - Use
errors.Is/errors.Asinstead of direct comparison (Go 1.13+) - Migrate deprecated crypto packages (Go 1.24+) — security critical
- Before bumping to
go 1.27, resolve removedGODEBUGkeys andcrypto/tls.Config.Randcallers (Go 1.27+) — see the risk checklist above; a staleGODEBUGvalue now fails the build
Medium priority (readability and maintainability)
- Replace
interface{}withany(Go 1.18+) - Use
min/maxbuiltins (Go 1.21+) - Use
rangeover int (Go 1.22+) - Use
slicesandmapspackages (Go 1.21+) - Use
cmp.Orfor default values (Go 1.22+) - Use
sync.OnceValue/sync.OnceFunc(Go 1.21+) - Use
sync.WaitGroup.Go(Go 1.25+) - Use
t.Context()in tests (Go 1.24+) - Use
b.Loop()in benchmarks (Go 1.24+) - Use generic methods for helpers scoped to one type, and
strings.CutLast/bytes.CutLastinstead ofLastIndexslicing (Go 1.27+) - Migrate to the
encoding/json/v2API — 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)
- Migrate to
slogfrom third-party loggers (Go 1.21+) - Adopt iterators where they simplify code (Go 1.23+)
- Replace
sort.Slicewithslices.SortFunc(Go 1.21+) - Use
strings.SplitSeqand iterator variants (Go 1.24+) - Move tool deps to
go.modtool directives (Go 1.24+) - Enable PGO for production builds (Go 1.21+)
- Upgrade to golangci-lint v2 with modernize linter (golangci-lint v2.6.0+)
- Add
govulncheckto CI pipeline - Set up monthly modernization CI pipeline
- Replace
google/uuid/gofrs/uuidwith the stdlibuuidpackage, after checking for RFC-variant features the stdlib doesn't cover (Go 1.27+) - Run
go fix ./...after a toolchain upgrade to apply the safe automated transformations (Go 1.27+) - 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-refactoringskill for staging a large modernization sweep as small human-reviewed PRs instead of one big worktree sweep.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

