Rename Go identifiers to follow idiomatic naming conventions.
npx skills add https://github.com/muratmirgun/gophers --skill go-naming-muratmirgun
Please help me install this Agent Skill. Skill: go-naming Source: https://github.com/muratmirgun/gophers/tree/main/skills/go-naming Command: npx skills add https://github.com/muratmirgun/gophers --skill go-naming-muratmirgun
This Skill helps you name Go packages, types, functions, variables, constants, errors, and options in ways that match idiomatic Go, reduce stuttering, and make code easier to read and review.
Get prefixes, util package names, shadowing built-ins, and inconsistent error strings.Ask the AI to rename your Go identifiers so they follow idiomatic Go naming rules and avoid stuttering, bad initialisms, and non-standard API patterns.
High-intent search queries and answers about installing and using this skill.
Idiomatic Go identifiers use MixedCaps, apply proper initialism casing, and adjust length based on scope. This standardizes packages, types, functions, receivers, constants, and enums to match community expectations and pass code reviews reliably.
To avoid stuttering and bad initialisms in Go API design, rename identifiers so they follow standard constructor, accessor, and option patterns. This prevents redundant package prefixes and ensures consistent initialism casing across your codebase.
Structuring Go sentinel and typed errors during refactoring involves standardizing their names and message strings to consistent conventions. This ensures errors are easily identifiable and match standard Go error handling patterns.
Go code reviews often fail over Get prefixes because idiomatic Go omits them from getter names. Boolean fields and enum zero values must also follow specific naming conventions to avoid shadowing built-ins and failing review.
Yes, you can apply standard naming conventions to Go receivers and options. This ensures receiver names are short and consistent, while option patterns follow idiomatic functional options structures used in production Go code.
berksunduriProvide Go naming convention guidelines for identifiers, constants, structs, and interfaces.
RaNDoM6913Detect outdated Go patterns and propose modern idioms for Go 1.21–1.24.
R2W1csLint and validate JavaScript and Python code for syntax and style issues.
rondevzEnforce Go style principles and formatting guidelines across codebases.