Review and rewrite Go functions, signatures, and constructors for idiomatic conventions.
npx skills add https://github.com/muratmirgun/gophers --skill go-functions
Please help me install this Agent Skill. Skill: go-functions Source: https://github.com/muratmirgun/gophers/tree/main/skills/go-functions Command: npx skills add https://github.com/muratmirgun/gophers --skill go-functions
This Skill helps you design Go functions that are easier to read, safer to call, and more consistent across a codebase. It reduces common API mistakes like pointer-to-interface parameters, unclear boolean flags, and poorly formatted multi-line signatures.
f suffix for printf-style helpers and encourages %q for safe string interpolation in errors and logs.Use the go-functions skill to review this Go file and rewrite its functions, signatures, and constructors to follow the repository’s function-design conventions.
High-intent search queries and answers about installing and using this skill.
To design Go function signatures for better API readability, keep short signatures on one line, wrap long parameter lists consistently, and use named options or typed parameters instead of naked booleans to ensure call-site clarity.
The correct way to order functions in a Go file is to follow a predictable sequence: types first, then constructors, exported methods, unexported helpers, and finally utilities, which keeps the codebase organized and maintainable.
Choosing between pointer and value receivers in Go requires maintaining consistency across methods and avoiding pointer-to-interface parameters, ensuring correct interface implementation and safe memory handling.
Naming conventions for printf-style helpers in Go require adding an `f` suffix to the function name and using `%q` for safe string interpolation in errors and logs to ensure vet-friendly formatting.
Yes, you can refactor existing constructors in your Go codebase by applying consistent function organization, signature clarity, and return-value shaping to produce idiomatic and vet-friendly APIs.
You should avoid passing pointers to interfaces in Go functions because interfaces already handle underlying pointer semantics internally, making explicit pointer-to-interface parameters redundant and a common API design mistake.
samberEnforce Go naming conventions for packages, types, and variables.
LuohaothuAnalyze modified Go files using vet and staticcheck, reporting prioritized, idiomatic improvements.
haipham22Design and validate Go type APIs for interface placement and constructor returns.
ncaqEnforce nixpkgs naming conventions for files, variables, and packages.