技能 golang-naming
📦
golang-naming
v1.2.1 內容修訂 r1 安全 ⚙️ 外部命令📁 檔案系統存取⚡ 包含腳本🌐 網路存取
Improve Go Naming Across Your Codebase
Inconsistent Go names make APIs and reviews harder to understand. This skill provides focused conventions and examples for choosing clear, consistent names.
支援: Codex Code(CC)
使用我的智慧代理安裝
將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。
智能體請求
Review the Skillstore skill "golang-naming" from https://skillstore.io/skills/samber-golang-naming.md and its manifest at https://skillstore.io/api/skills/samber-golang-naming/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。
Agent 可讀資源
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。
測試它
正在使用「golang-naming」。 Review the names userSlice, countInt, contextCtx, and userId.
預期結果:
- Use users instead of userSlice to describe the contents rather than the storage type.
- Use count instead of countInt because the type already communicates that it is an integer.
- Use ctx instead of contextCtx to follow common Go parameter naming.
- Use userID instead of userId to keep the initialism consistently capitalized.
正在使用「golang-naming」。 Choose constructor and error names for an apiclient package with one primary Client type.
預期結果:
- Prefer New for the primary constructor so the package-qualified name avoids repeating Client.
- Use ErrNotFound for a sentinel error and ResponseError for a custom error type.
- Under this skill's style, prefix the sentinel message with apiclient to identify its origin.
正在使用「golang-naming」。 Review a TaskState enum whose zero value is TaskStatePending.
預期結果:
- The skill recommends TaskStateUnknown as an explicit zero-value sentinel.
- Keep the TaskState prefix on enum values for clarity.
- Check persisted values and API contracts before changing existing numeric assignments.
安全審計
安全v1 • 2026/10/15 開啟版本化報告
All 127 static findings are false positives in naming documentation and evaluation fixtures. Backticks format examples, the traversal match occurs in placeholder comments, and the import match is ordinary Go syntax. No evidence found of malicious execution, data exfiltration, system reconnaissance, or prompt injection in the seven reviewed files.
7
已掃描檔案
1,186
分析行數
0
複核項目
0
已忽略的誤報
風險因素
⚙️ 外部命令 (50)
evals/evals.json:6 evals/evals.json:7 evals/evals.json:35 evals/evals.json:68 evals/evals.json:97 evals/evals.json:126 evals/evals.json:127 evals/evals.json:131 evals/evals.json:135 evals/evals.json:139 evals/evals.json:143 evals/evals.json:155 evals/evals.json:160 evals/evals.json:164 evals/evals.json:168 evals/evals.json:172 evals/evals.json:176 evals/evals.json:180 evals/evals.json:188 evals/evals.json:217 evals/evals.json:242 evals/evals.json:300 evals/evals.json:325 evals/evals.json:354 evals/evals.json:383 SKILL.md:22 SKILL.md:38 SKILL.md:39 SKILL.md:40 SKILL.md:41 SKILL.md:42 SKILL.md:43 SKILL.md:44 SKILL.md:45 SKILL.md:46 SKILL.md:47 SKILL.md:48 SKILL.md:49 SKILL.md:50 SKILL.md:51 SKILL.md:52 SKILL.md:53 SKILL.md:54 SKILL.md:55 SKILL.md:56 SKILL.md:57 SKILL.md:58 SKILL.md:59 SKILL.md:60 SKILL.md:61
📁 檔案系統存取 (1)
⚡ 包含腳本 (1)
🌐 網路存取 (1)
最近一次完成的靜態與語意稽核未偵測到已確認的安全發現。這並不能證明該 Skill 沒有副作用。
審計單位: codex
分享與引用此報告
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。
複製報告連結
https://skillstore.io/skills/samber-golang-naming/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/samber-golang-naming?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/samber-golang-naming?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/samber-golang-naming/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/samber-golang-naming.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>學術引用 (APA · BibTeX · CFF)
APA 引用
samber. (2026). golang-naming security audit report (audit version 1) [Author version 1.2.1]. Skillstore. https://skillstore.io/skills/samber-golang-naming/audits/1BibTeX 引用
@techreport{samber-samber-golang-naming-2026,
author = {samber},
title = {golang-naming security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/samber-golang-naming/audits/1},
note = {Author version 1.2.1}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "golang-naming security audit report (audit version 1)"
version: "1.2.1"
type: report
authors:
- name: "samber"
date-released: "2026-10-15"
url: "https://skillstore.io/skills/samber-golang-naming/audits/1"
identifiers:
- type: other
value: "skillstore:samber-golang-naming:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 評分
評分依據 證據置信度: 中 45
架構
100
可維護性
87
內容
65
社群
91
規範符合度
你可以打造什麼
Learn Go Naming Conventions
Compare familiar naming habits with Go conventions for variables, acronyms, constants, and receivers.
Review Public API Names
Evaluate package names, constructors, interfaces, options, and errors before publishing a Go library.
Standardize Team Terminology
Identify inconsistent domain names and prepare naming recommendations that respect established project conventions.
試試這些提示
Explain a Naming Choice
Compare userId and userID in Go. Recommend one and explain acronym casing.
Review a Go Snippet
Review the Go snippet below for naming only: [snippet]. Suggest replacements for variables, receivers, and getters. Explain each recommendation.
Design Consistent API Names
Review public names for [package] with [types and functions]. Recommend constructor, option, interface, and error names. Consider call sites and existing conventions.
Plan a Naming Refactor
Assess [packages or files] for inconsistent domain names. Propose a rename plan, identify public API risks, and separate recommendations from required compatibility checks.
最佳實務
- Provide package context and representative call sites when asking for naming recommendations.
- Reconcile the skill's preferences with established project conventions and compatibility requirements.
- Use language-server renaming and run relevant tests when applying identifier changes.
避免
- Treating every style preference as a compiler requirement or universal Go rule.
- Renaming exported identifiers without checking downstream callers and interface contracts.
- Using broad text replacement for semantic renames across a workspace.
常見問題
Which tools does this skill support?
The skill declares compatibility with Codex and Claude Code. Its guidance applies to Go projects.
What naming areas does it cover?
It covers packages, files, identifiers, constructors, methods, interfaces, constants, enums, errors, and tests.
Does it automatically enforce naming rules?
No executable enforcement tool is included. The skill references linters and separate skills for automation.
Can it safely rename every reference?
The skill recommends separate gopls tooling for workspace-wide renames. Review public API compatibility and test the resulting changes.
Are all recommendations official Go requirements?
No. Some rules are opinionated, including mandatory boolean prefixes and lowercase acronyms in error messages. Apply project conventions and engineering judgment.
Can company naming conventions take precedence?
Yes. The skill states that a company skill explicitly superseding its naming guidance takes precedence.
開發者詳細資訊
作者
samber授權
MIT
作者版本
v1.2.1
Skillstore 修訂
r1
引用
0ce0f4139d4ad3a3ead919503e26f557dfc436ca
維護新鮮度
2026/10/16
使用量
1 次下載 · 0 次瀏覽
檔案結構