Go Linting

This is a practical guide to setting up golangci-lint with opinionated but sensible defaults. It recommends five core linters (errcheck, goimports, revive, govet, staticcheck) and emphasizes consistent linting over any particular toolset. The setup script generates a working config in one command, and the documentation covers nolint directives, CI integration, and when to add security or complexity checks. The advice is clearly derived from the Uber Style Guide, which means it's battle-tested on large codebases. If you're starting a Go project or tired of inconsistent linting across your repos, this gives you a solid baseline without drowning you in 50+ linter options.

skills.sh installs: 1.3K
GitHub stars: 193
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add cxuu/golang-skills --skill go-linting --agent claude-code

Installs into .claude/skills of the current project.

Files

Go Linting

Core Principle

More important than any "blessed" set of linters: lint consistently across a codebase.

Consistent linting helps catch common issues and establishes a high bar for code quality without being unnecessarily prescriptive.

Resource Routing

scripts/setup-lint.sh - Run when generating a .golangci.yml, validating the first lint pass, or producing JSON metadata.
assets/golangci.yml - Use as the v2 golangci-lint baseline for established projects.

Setup Procedure

Create .golangci.yml with scripts/setup-lint.sh or copy assets/golangci.yml
Run golangci-lint run ./...
If errors appear, fix them category by category (formatting first, then vet, then style)
Re-run until clean

After generating .golangci.yml, run golangci-lint config verify --config .golangci.yml to verify the configuration schema before relying on lint results.