菜单
Plan and apply evidence-based Go modernization for language, standard-library, test, and tooling changes. Use when upgrading a module toward Go 1.26, replacing deprecated APIs, adopting new library helpers, or reviewing modernization risk.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/matdev83/golang-curated-agent-skills --skill golang-modernize命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Go benchmark and profile workflow: b.Loop, benchstat, pprof, trace, compiler diagnostics, and regression gates.
Go command-line applications: choose a framework, build commands and flags, layer configuration, handle output and exit status, support signals and completion, and test behavior.
Practical Go style for readable, idiomatic code: formatting, control flow, declarations, API boundaries, comments, zero values, and reviewable organization. Use when writing or reviewing Go code where clarity matters beyond gofmt.
正在显示 SKILL.md
| name | golang-modernize |
| description | Plan and apply evidence-based Go modernization for language, standard-library, test, and tooling changes. Use when upgrading a module toward Go 1.26, replacing deprecated APIs, adopting new library helpers, or reviewing modernization risk. |
Modernization is a compatibility change, not a style sweep. Start from the module’s declared Go version, supported platforms, public API promises, and a measured workload.
go.mod, toolchain files, build tags, CI, and release/support policy. Confirm the installed toolchain and whether the change may alter language or standard-library semantics.go line. Run go fix or a targeted analyzer only after reviewing the diff; inspect each automated rewrite.gofmt, focused tests, go vet, and package/build checks. For performance changes, compare representative benchmark distributions with benchstat.Check whether slices, maps, cmp, min/max, range-over-integer, any, improved iterators, testing.T.Context, testing/synctest, b.Loop, and testing artifact support simplify code in the actual target module. Confirm the exact API in the installed toolchain before using it. Do not label older features as new: httputil.ReverseProxy.Rewrite has existed since Go 1.20, and context.WithoutCancel since Go 1.21.
Use math/rand/v2 only after considering deterministic seeds, output compatibility, and the public behavior of the old generator. Use os.Root (where the module’s supported Go version permits) for directory-scoped file operations instead of inventing path-prefix security checks.
PGO profiles must come from the production-like binary and representative workload. Build the exact program with the profile, compare a baseline and optimized build under the same conditions, and keep the profile with the source/build process that produced it. Do not promise a fixed percentage gain and do not produce a generic profile from an unrelated benchmark.
Treat compiler, linter, dependency, and CI upgrades as supply-chain changes: review release notes, checksums, compatibility, and reproducibility. A modernization is complete only when tests and supported-platform builds pass and any behavior change is explicitly accepted. See tooling and measurement and version notes.