Go Code Style
Go style conventions that need human judgment — line breaking, declarations, control-flow clarity, when comments help vs hurt
- What
- Go style conventions that need human judgment — line breaking, declarations, control-flow clarity, when comments help vs hurt
- Cost
- Free
- Needs
- a Go project (the go toolchain)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a Go style skill built on a simple split: linters handle formatting, this handles clarity. It covers line length and semantic breaking (4+ arguments = one per line), variable declarations, control-flow clarity, and when comments help versus hurt — with an orchestration mode that fans out sub-agents over independent style concerns for large codebases. Distinct from the already-published samber skills (golang-testing, golang-safety, golang-benchmark, golang-troubleshooting, influence-and-negotiation) — this one is about readable style, and it explicitly defers naming to golang-naming and doc comments to golang-documentation. By @samber, listed here with credit to its creator. Honest caveats: "clear is better than clever" is a judgment call — the skill gives you the rules, your team still decides the taste; ignoring a rule requires a code comment, by design. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Go Code Style is a free Muse skill covering Go style conventions that need human judgment, while linters handle formatting. It covers line length and semantic breaking, variable declarations, control-flow clarity, and when comments help versus hurt, with an orchestration mode fanning out sub-agents over style concerns for large codebases.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 8e899e2Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Go project (the go toolchain) Install "Go Code Style" for me. Go style conventions that need human judgment — line breaking, declarations, control-flow clarity, when comments help vs hurt Repository: https://raw.githubusercontent.com/samber/cc-skills-golang/8e899e20ff0cd4dc524af3993e4c62d8ee8c5717/skills/golang-code-style/SKILL.md Pinned version: install the code at commit 8e899e20ff0cd4dc524af3993e4c62d8ee8c5717 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the samber-golang-code-style skill from the repository into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "samber-golang-code-style". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 8e899e2 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.