Apply idiomatic Go naming conventions to identifiers and code elements.
npx skills add https://github.com/Qunnnn/agents --skill go-naming-qunnnn
Please help me install this Agent Skill. Skill: go-naming Source: https://github.com/Qunnnn/agents/tree/main/skills/go/go-naming Command: npx skills add https://github.com/Qunnnn/agents --skill go-naming-qunnnn
This Skill helps developers avoid inconsistent or unclear naming choices in Go code by applying established naming conventions that improve readability and maintainability.
Ask the go-naming skill to review my Go code and suggest more idiomatic names for packages, types, variables, and errors.
High-intent search queries and answers about installing and using this skill.
Idiomatic Go naming conventions apply MixedCaps for identifiers, concise receiver names, clear package names, and specific patterns for acronyms, constructors, and errors to improve code readability and maintainability.
To review and refactor Go code for naming consistency, apply established rules for visibility, interfaces, receivers, and error patterns to ensure identifiers remain predictable and easy for other developers to understand.
Yes, Go naming rules require specific visibility patterns where exported identifiers use capitalized MixedCaps and unexported ones use lowercase MixedCaps, ensuring clear access control across packages and files.
The best way to name receiver variables in Golang is to use concise, consistent names across methods, typically a one or two-letter abbreviation of the type, to improve readability without cluttering the code.
In Go API design, acronyms should maintain consistent capitalization like MixedCaps, while error naming patterns should clearly indicate the failure context to ensure predictable and understandable API interfaces.
JylhisValidate Go identifier naming against idiomatic MixedCaps conventions.
BarryYinValidate feature-level integration and cross-task consistency across implemented tasks.
zajcaConfigure golangci-lint with recommended Go linters for static analysis.
vankichiReview Go code against style, naming, error handling, and concurrency guidelines.
