メニュー
Choose idiomatic, searchable Go names for packages, files, identifiers, receivers, methods, interfaces, errors, tests, and examples. Use when naming new APIs or reviewing names for clarity and compatibility.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/matdev83/golang-curated-agent-skills --skill golang-namingコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Go benchmark and profile workflow: b.Loop, benchstat, pprof, trace, compiler diagnostics, and regression gates.
Go command-line applications: choose a framework, build commands and flags, layer configuration, handle output and exit status, support signals and completion, and test behavior.
Practical Go style for readable, idiomatic code: formatting, control flow, declarations, API boundaries, comments, zero values, and reviewable organization. Use when writing or reviewing Go code where clarity matters beyond gofmt.
SKILL.md を表示中
| name | golang-naming |
| description | Choose idiomatic, searchable Go names for packages, files, identifiers, receivers, methods, interfaces, errors, tests, and examples. Use when naming new APIs or reviewing names for clarity and compatibility. |
Names should make the smallest useful promise. Prefer the vocabulary already used by the package and its callers; do not rename a public symbol merely to satisfy a preference.
URL, HTTP, ID, JSON).i, err, ctx) and descriptive when values live longer or have similar peers.http.Server, not http.HTTPServer; user.Name, not user.UserName unless the distinction matters.NewType for constructors when that convention is useful, but do not create constructors just to validate a zero-value-safe type.Enabled, HasItems, CanRetry) and avoid double negatives.Receiver names are short and consistent within a type; they are not part of the method’s API. A method named Read does not implement io.Reader by name alone—the exact Read([]byte) (int, error) signature and method set are required.
Package names are lowercase, concise, and singular where natural; avoid generic names like util, common, or misc. A cmd/ tree is a useful convention for commands, not a Go requirement. The internal/ rule is lexical: code under an internal directory may be imported only by code within that directory’s parent tree, regardless of module boundaries.
Use file suffixes and build constraints to communicate platform or role (_test.go, _linux.go, _windows.go). Keep generated-file markers intact. File names do not determine package visibility.
Prefer names that describe behavior or domain concepts, not implementation details. Interface names may use -er when the single behavior is clear (io.Reader), but multi-method interfaces need not be forced into that suffix. Keep interfaces small and define them near the consumer.
Sentinel errors use Err plus a meaningful noun/adjective (ErrNotFound). Custom error types describe the failure (ParseError) and expose fields only when callers need them. Test names state behavior (TestParserRejectsEmptyInput); subtest names should distinguish cases without encoding incidental implementation.
See identifier details, functions and methods, packages and files, types and errors, and testing names.