Edge Copy setup link
Skill evidence / Golang Naming

Golang Naming

Go (Golang) naming conventions : covers packages.

samber/cc-skills-golangpinned 19a0626
✓ Security state: reviewed

2 static scans, 0 counted findings.

Recorded for this package revision; Edge checks the exact bundle again when your agent loads it.

SKILL.md7 files · 58.7 KB
From samber’s public repository. Edge did not write or edit this skill.

What this skill does for you

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.

Quoted from the skill description in the pinned source

Use it with Edge

Set up Edge for me: read getedge.cc/SKILL.md and follow it. Then use Edge to load the golang-naming skill from samber/cc-skills-golang.

Paste it into Claude, ChatGPT, Codex or Cursor.

Or read the skill source first.

Try Golang Naming in your agent.

Go (Golang) naming conventions : covers packages.