Enforce Go naming conventions for identifiers, APIs, errors, and tests.
npx skills add https://github.com/dmwin72015/netdisk --skill golang-naming-dmwin72015
Please help me install this Agent Skill. Skill: golang-naming Source: https://github.com/dmwin72015/netdisk/tree/main/.agents/skills/golang-naming Command: npx skills add https://github.com/dmwin72015/netdisk --skill golang-naming-dmwin72015
Go codebases degrade when naming drifts, making it harder to navigate, review, and refactor; this skill enforces consistent, idiomatic identifier and API naming so code remains readable and tool-friendly.
Ask an AI agent: "Refactor this Go API draft to follow golang-naming conventions for acronyms, constructors, boolean predicates, error strings, and test subcase names."
High-intent search queries and answers about installing and using this skill.
Go naming conventions for constructors use the New prefix, while functional options use the With* suffix, such as WithContext. These standard API patterns prevent readability issues and ensure your codebase remains tool-friendly and easy to navigate.
To name errors and test subcases in Go code reviews, enforce lowercase error strings and lowercase subtest names. Use the Err* prefix for sentinel errors and the Error suffix for custom error types to maintain consistency.
Idiomatic Go API design does not use the Get prefix for getters. Instead, name boolean predicates with Is, Has, or Can prefixes, and rely on MixedCaps identifiers without underscores to prevent tooling issues.
You need to apply MixedCaps rules for Go package and file naming whenever writing new code or refactoring existing packages. This prevents inconsistent identifiers and ensures exported versus unexported identifiers are immediately recognizable.
To handle acronyms in Go identifier names, enforce consistent capitalization rules for acronyms within MixedCaps identifiers. Treating acronyms consistently prevents naming drift and keeps code readable during pull requests.
The best way to standardize Go naming across a large codebase is to enforce consistent constructor suffixes, boolean predicates, and error conventions. Applying these rules during refactoring prevents readability degradation and tooling issues.
heyJordanParkerEvaluate identifiers to enforce consistent naming across codebases.
haipham22Apply idiomatic Go naming conventions to packages, identifiers, and tests.
tokiouEnforce Go naming conventions for identifiers, errors, and tests.
YuunqiLiuEnforces consistent formatting and naming standards for RTL designs.
