domains / families / software-engineering / golang-refactoring

golang-refactoring

separate

Golang refactoring — safe, at-scale restructuring of existing Go code: a coverage-adaptive safety net, behavior-preserving transforms (gopls Rename/Extract, `gofmt -r`, `gopatch`), the Fowler catalog mapped to Go, breaking import cycles, and small stacked PRs. Apply when a function or type has grown too large, a code smell blocks a feature, or the user asks to refactor Go code — also for renaming at scale, extracting functions or interfaces, moving code between packages, or planning a multi-step refactor. Target styles owned elsewhere → See `samber/cc-skills-golang@golang-naming` (renames), `samber/cc-skills-golang@golang-project-layout` (splits), `samber/cc-skills-golang@golang-modernize` (idioms), `samber/cc-skills-golang@golang-code-style` (control flow), `samber/cc-skills-golang@golang-design-patterns` (patterns/DI).

When to use

• refactoring Go code
• renaming at scale
• extracting functions or interfaces
• moving code between packages
• planning a multi-step refactor
• breaking import cycles
• restructuring large functions or types

When not to use

• golang-naming
• golang-project-layout
• golang-modernize
• golang-code-style
• golang-design-patterns

Skill page

Source