golang-naming

Go (Golang) naming conventions — covers packages, constructors, structs, interfaces, constants, enums, errors, booleans, receivers, getters/setters, functional options, acronyms, test functions, and subtest names. Use this skill when writing new Go code, reviewing or refactoring, choosing between naming alternatives (New vs NewTypeName, isConnected vs connected, ErrNotFound vs NotFoundError, StatusReady vs StatusUnknown at iota 0), debating Go package names (utils/helpers anti-patterns), or asking about Go naming best practices. Also trigger when the user mentions MixedCaps vs snake_case, ALL_CAPS constants, Get-prefix on getters, or error string casing. Do NOT use for general Go implementation questions that don't involve naming decisions.

1.34x

Quality

88%

Does it follow best practices?

Impact

90%

1.34x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Evaluation results

88%

19%

Message Broker Client Library

Functional options pattern naming

Criteria

Without context

With context

Options struct name

Option function type singular

100%

With* option functions

100%

Default options factory

100%

Constants MixedCaps not ALL_CAPS

100%

Constants by role not value

100%

No Struct/Object/Data suffix

100%

No stuttering in option types

100%

Constructor uses New or NewTypeName

100%

Functional options used for 3+ params

100%

88%

41%

JWT Token Validator Tests

Test naming conventions

Criteria

Without context

With context

input field name

expected field prefix

100%

Subtest names fully lowercase

83%

100%

Subtest acronyms lowercase

100%

Test helper must prefix

100%

Test function naming pattern

50%

100%

Subcase underscore separator

100%

Table test struct has name field

100%

No exported test helpers

100%

94%

CSV Transformation Library

File naming and function naming

Criteria

Without context

With context

File names lowercase

100%

File names use underscores

100%

Value-returning functions are nouns

33%

50%

Action functions are verbs

100%

Ambiguous params have descriptive names

100%

No type in variable names

100%

No package stutter in functions

40%

100%

Test file naming

100%

Descriptive short params for clear types

100%

Repository: samber/cc-skills-golang
Commit: e9761db

Evaluated: 1 day ago
Agent: Claude Code
Model: Claude Sonnet 4.6

Table of Contents

Message Broker Client Library JWT Token Validator Tests CSV Transformation Library

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.