- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add samber/cc-skills-golang --skill golang-modernize -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add samber/cc-skills-golang --skill golang-modernize -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add samber/cc-skills-golang --skill golang-modernize -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add samber/cc-skills-golang --skill golang-modernize -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/samber/cc-skills-golang/tree/HEAD/skills/golang-modernize게시자 제공
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:
/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.
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.
When invoked:
go.mod or go.work to determine the current Go version (go directive)go.mod is behind.modernize in the project root — this file contains previously ignored suggestions; do NOT re-suggest anything listed theregolangci-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/golang-modernize or in CI, scan and suggest across the entire codebase.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..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
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.
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.
For detailed before/after examples for each Go version (1.21–1.27) and general modernizations, see Go version modernizations.
For CI tooling, govulncheck, PGO, golangci-lint v2, and AI-powered modernization pipelines, see Tooling modernization.
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.
When modernizing a codebase, prioritize changes by impact:
math/rand with math/rand/v2 (Go 1.22+) — remove rand.Seed callsos.Root for user-supplied file paths (Go 1.24+) — prevents path traversalgovulncheck (Go 1.22+) — catch known vulnerabilitieserrors.Is/errors.As instead of direct comparison (Go 1.13+)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 buildinterface{} with any (Go 1.18+)min/max builtins (Go 1.21+)range over int (Go 1.22+)slices and maps packages (Go 1.21+)cmp.Or for default values (Go 1.22+)sync.OnceValue/sync.OnceFunc (Go 1.21+)sync.WaitGroup.Go (Go 1.25+)t.Context() in tests (Go 1.24+)b.Loop() in benchmarks (Go 1.24+)strings.CutLast/bytes.CutLast instead of LastIndex slicing (Go 1.27+)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+)slog from third-party loggers (Go 1.21+)sort.Slice with slices.SortFunc (Go 1.21+)strings.SplitSeq and iterator variants (Go 1.24+)go.mod tool directives (Go 1.24+)govulncheck to CI pipelinegoogle/uuid/gofrs/uuid with the stdlib uuid package, after checking for RFC-variant features the stdlib doesn't cover (Go 1.27+)go fix ./... after a toolchain upgrade to apply the safe automated transformations (Go 1.27+)samber/cc-skills-golang@golang-continuous-integrationSee 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.
samber/cc-skills-golang@golang-refactoring skill for staging a large modernization sweep as small human-reviewed PRs instead of one big worktree sweep.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 warnin
---name: golang-modernizedescription: Modernize Golang code to use recent language features, standard library improvements, and idiomatic patterns…---# skills/golang-modernize/SKILL.md개요
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).
FAQ
게시자에게서 skills/golang-modernize/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/samber/cc-skills-golang에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.