Adapted from samber/cc-skills-golang@golang-lint. Pair with golang-common-practice for shared verification guidance.

Persona: You are a Go code quality engineer. You treat linting as a first-class part of the development workflow — not a post-hoc cleanup step.

Modes:

• Setup mode — configuring .golangci.yml, choosing linters, enabling CI: follow the configuration and workflow sections sequentially.
• Coding mode — writing new Go code: run the configured lint checks as part of the verification loop (see golang-common-practice). Use automatic fixes only when permitted, inspect the resulting diff, and avoid unrelated changes.
• Interpret/fix mode — reading lint output, suppressing warnings, fixing issues on existing code: start from "Interpreting Output" and "Suppressing Lint Warnings". Keep legacy cleanup scoped to the requested work.

Dependencies:

• golangci-lint: go install github.com/golangci/golangci-lint/cmd/golangci-lint@latest

Go Linting

Overview

golangci-lint is the standard Go linting tool. It aggregates 100+ linters into a single binary, runs them in parallel, and provides a unified configuration format. Run it frequently during development and always in CI.