golang-code-style
Improve Go Code Style
Go code can pass formatting checks while still being hard to read. This skill guides Claude, Codex, and Claude Code toward clearer style choices.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "golang-code-style" from https://skillstore.io/skills/samber-golang-code-style.md and its manifest at https://skillstore.io/api/skills/samber-golang-code-style/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "golang-code-style". A Go handler has nested validation and returns nil slices for empty results.
Expected outcome:
- Use early returns so validation failures exit before the happy path.
- Return initialized empty slices for success cases with no results.
- Keep the main response-building logic at shallow indentation.
Using "golang-code-style". A service function accepts many separate configuration parameters.
Expected outcome:
Suggest grouping related inputs into an options struct, with context first and the primary dependency near the front.
Using "golang-code-style". A review asks whether a pointer parameter is needed for a string.
Expected outcome:
Recommend passing the string by value unless nil has meaning or the function must mutate a referenced value.
Security Audit
SafeStatic alerts were reviewed in context and adjudicated as false positives. Backtick matches are Markdown code spans, fenced Go examples, and eval prompt strings rather than shell execution. The only URL is homepage metadata, and no prompt injection or malicious intent was found.
Risk Factors
⚙️ External commands (74)
🌐 Network access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/samber-golang-code-style/audits/3?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/samber-golang-code-style?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/samber-golang-code-style?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/samber-golang-code-style/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/samber-golang-code-style.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
samber. (2026). golang-code-style security audit report (audit version 3) [Author version 1.2.0]. Skillstore. https://skillstore.io/skills/samber-golang-code-style/audits/3BibTeX citation
@techreport{samber-samber-golang-code-style-2026,
author = {samber},
title = {golang-code-style security audit report (audit version 3)},
institution = {Skillstore},
year = {2026},
number = {3},
url = {https://skillstore.io/skills/samber-golang-code-style/audits/3},
note = {Author version 1.2.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "golang-code-style security audit report (audit version 3)"
version: "1.2.0"
type: report
authors:
- name: "samber"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/samber-golang-code-style/audits/3"
identifiers:
- type: other
value: "skillstore:samber-golang-code-style:audit:3"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Review a Go Pull Request
Find readability issues in control flow, declarations, function shape, and file organization before merging.
Set Team Style Standards
Create a practical checklist for style decisions that are harder for automated linters to enforce.
Guide AI Code Edits
Keep generated Go code readable when prompts ask for compact code, nested branches, or excessive parameters.
Try These Prompts
Review my Go file for readable style. Focus on line length, variable declarations, early returns, and initialized empty collections.
Refactor this Go function for clarity. Preserve behavior, reduce nesting, remove unnecessary else blocks, and explain the style changes.
Create a concise Go code style checklist for this repository. Align it with existing patterns and note rules linters cannot enforce.
Review this Go codebase using separate style concerns. Report findings for control flow, function design, collection initialization, and file organization.
Best Practices
- Pair this skill with gofmt, gofumpt, and goimports for mechanical formatting.
- Ask for behavior-preserving edits before style refactors.
- Use repository conventions when they conflict with generic style guidance.
Avoid
- Using the skill to replace tests, linters, or compiler checks.
- Applying every guideline mechanically without considering readability.
- Requesting naming or documentation rules that belong to linked skills.
Frequently Asked Questions
Does this skill format Go code automatically?
Can it review existing Go code?
Does it replace a linter?
Does it cover naming rules?
Can it help with large repositories?
Is it specific to Claude Code?
Developer Details
Author
samberLicense
MIT
Author version
v1.2.0
Skillstore revision
r1
Ref
e397ce5a135369cd6def89cb6400d013e2f68f2f
Maintenance freshness
7/18/2026
Usage
2 downloads · 0 views
File structure