golang-naming
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.
Installer avec mon Agent
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
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.Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.
Ressources lisibles par les agents
Utilisez ces liens lorsqu’un Agent IA, un crawler ou un script a besoin d’un contexte propre au lieu de lire toute la page.
Tester
Utilisation de « golang-naming ». Review the names userSlice, countInt, contextCtx, and userId.
Résultat attendu:
- 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.
Utilisation de « golang-naming ». Choose constructor and error names for an apiclient package with one primary Client type.
Résultat attendu:
- 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.
Utilisation de « golang-naming ». Review a TaskState enum whose zero value is TaskStatePending.
Résultat attendu:
- 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.
Audit de sécurité
SûrAll 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.
Facteurs de risque
⚙️ Commandes externes (50)
📁 Accès au système de fichiers (1)
⚡ Contient des scripts (1)
🌐 Accès réseau (1)
Partager et citer ce rapport
Partagez le rapport d’évaluation versionné, le badge neutre, la carte intégrable et les citations. Skillstore présente les preuves sans décider si ce Skill est sûr.
Copier le lien du rapport
https://skillstore.io/skills/samber-golang-naming/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/samber-golang-naming?utm_source=security_passport_badge)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>Carte intégrable
<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>Citations académiques (APA · BibTeX · CFF)
Citation 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/1Citation BibTeX
@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"
Score Skillstore
Pourquoi ce score Niveau de confiance des preuves: MoyenCe que vous pouvez créer
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.
Essayez ces prompts
Compare userId and userID in Go. Recommend one and explain acronym casing.
Review the Go snippet below for naming only: [snippet]. Suggest replacements for variables, receivers, and getters. Explain each recommendation.
Review public names for [package] with [types and functions]. Recommend constructor, option, interface, and error names. Consider call sites and existing conventions.
Assess [packages or files] for inconsistent domain names. Propose a rename plan, identify public API risks, and separate recommendations from required compatibility checks.
Bonnes pratiques
- 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.
Éviter
- 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.
Foire aux questions
Which tools does this skill support?
What naming areas does it cover?
Does it automatically enforce naming rules?
Can it safely rename every reference?
Are all recommendations official Go requirements?
Can company naming conventions take precedence?
Détails du développeur
Auteur
samberLicence
MIT
Version de l’auteur
v1.2.1
Révision Skillstore
r1
Réf
0ce0f4139d4ad3a3ead919503e26f557dfc436ca
Récence de maintenance
16/10/2026
Utilisation
1 téléchargements · 0 vues
Structure de fichiers