스킬 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.에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.
에이전트가 읽기 쉬운 리소스
AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.
테스트해 보기
"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)
가장 최근에 완료된 정적·의미론적 감사에서 확인된 보안 발견 사항이 감지되지 않았습니다. 이는 스킬에 부작용이 없음을 증명하지 않습니다.
감사자: 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 조회
파일 구조