Refactor and review Go code for idiomatic patterns and standard-library practices.
npx skills add https://github.com/spf13/go-skills --skill go-spf13
Please help me install this Agent Skill. Skill: go Source: https://github.com/spf13/go-skills/tree/main/go Command: npx skills add https://github.com/spf13/go-skills --skill go-spf13
This Skill helps you write, review, and refactor Go code so it stays simple, readable, maintainable, and aligned with modern Go conventions instead of drifting into over-engineered, Java-style patterns.
Ask for a review or rewrite of your Go code and specify that you want idiomatic package structure, modern stdlib-based patterns, and practical refactoring suggestions.
High-intent search queries and answers about installing and using this skill.
To refactor Go code away from Java-style layers, reorganize applications by domain and purpose rather than artificial layers, flattening service/repository/controller structures into clear, simple package boundaries with minimal nesting.
The best way to structure Go packages is by domain-oriented design with clear boundaries, minimal nesting, and useful zero values, avoiding heavy frameworks in favor of standard-library-first APIs.
Idiomatic Go tests use table-driven tests, fakes, and stubs to ensure simple and maintainable coverage, aligning with standard-library-first tooling rather than heavy mocking frameworks.
Go concurrency needs context-aware goroutines to ensure safe execution, allowing channels and standard-library patterns to manage cancellation and lifecycle cleanly without leaking resources.
Handle error wrapping in modern Go by requiring clear error wrapping patterns, ensuring simple, readable, and maintainable code that aligns with modern Go conventions rather than over-engineered solutions.
Yes, you can refactor legacy Go code by applying modern standard-library practices, including generics and HTTP routing, to enforce idiomatic language patterns and flatten domain-focused structures.
Oruga420Provide idiomatic Go patterns for concurrency, error handling, and package design.
nimadorostkarEnforce idiomatic error handling and bounded concurrency in Go code.
vanstinatorRecommend production-ready Go libraries with a standard-library-first approach.
QunnnnEnforce idiomatic Go style and maintainable programming patterns in code reviews.
