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:
Install
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://github.com/samber/cc-skills-golang/blob/main/skills/golang-code-style/SKILL.md 1. Fetch the SKILL.md file for the samber-golang-code-style skill from the repository into a temporary folder and summarize what it does in one or two sentences. 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.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build 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 build before installing it.