Go Linting
golangci-lint done right — configuration, .golangci.yml as source of truth, nolint, legacy cleanup
- What
- golangci-lint done right — configuration, .golangci.yml as source of truth, nolint, legacy cleanup
- Cost
- Free
- Needs
- a Go toolchain (go) and golangci-lint (`go install github.com/golangci/golangci-lint/cmd/golangci-lint@latest` or brew)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — linting best practices for Go with golangci-lint: running linters, configuring `.golangci.yml` (the source of truth for which linters are enabled and how — includes a recommended production-ready configuration with 48 linters), suppressing warnings with nolint directives, interpreting lint output, and selecting linters. Three modes: setup (configure and enable CI), coding (run `golangci-lint run --fix` on modified files in the background while you keep implementing), and interpret/fix (read lint output, fix or suppress, with parallel sub-agents for large-scale legacy cleanup). Every Go project must have a `.golangci.yml`; treat linting as a first-class workflow step, not post-hoc cleanup. Not for wiring a lint step into GitHub Actions — that belongs to the already-listed samber-golang-continuous-integration. By @samber, listed here with credit to its creator. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a Go toolchain (go) and golangci-lint (`go install github.com/golangci/golangci-lint/cmd/golangci-lint@latest` or brew) Install "Go Linting" for me. golangci-lint done right: configuration, .golangci.yml as source of truth, nolint, legacy cleanup Repository: https://github.com/samber/cc-skills-golang/blob/main/skills/golang-lint/SKILL.md 1. Fetch the SKILL.md file for the samber-golang-lint 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-lint". 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. installing golangci-lint). 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.