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).
Install
KitScout test notes
Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.
Similar tools
rea-tool-design456,474 ★ Audit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and E
reverse-engineer-anything456,474 ★ Reverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and b
code-review323,337 ★ Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does th
codebase-design323,337 ★ Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interfac
domain-modeling323,337 ★ Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLO