golang-naming

Editorial and source context

What this Skill does

Golang Naming is a source-indexed Agent Skill for development & engineering work. Based on the SKILL.md description, it focuses on go (golang) naming conventions — covers packages, constructors, structs, interfaces, constants, enums,…. Use the linked GitHub file to confirm scope and prerequisites before enabling it.

What the author says

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.

Compatibility and requirements

• Use an agent runtime that supports Agent Skills and the linked SKILL.md format.
• Confirm the source repository's tools, SDKs, and platform prerequisites for seo and content work.

How to install or import it

• Open the linked GitHub SKILL.md and review its scope and setup instructions.
• Install or import the skill using the agent runtime's documented workflow.
• Run a small, non-sensitive test and verify the output before broader use.

Permissions and risks

• Review every command, file path, network request, dependency, and credential scope before enabling it.
• GitHub stars indicate popularity, not safety or correctness; validate the source and test with non-sensitive data.

Example workflows

• Ask an AI agent to apply Golang Naming to seo and content work described in the source record.
• Have the agent state assumptions, required tools, and expected output before using this development & engineering skill.
• Compare the result with the linked GitHub SKILL.md and verify it against your project requirements.