golang-lint

Create a .golangci.yml with version: "2" at the top, list linters under linters.enable, and put formatters like gofumpt under formatters.enable. Set run.timeout for large repos and use linters.settings for per-linter options like errcheck check-type-assertions.

Add //nolint:lintername on the flagged line with a justification comment, for example //nolint:errcheck // fire-and-forget logging. Never use bare //nolint, and enable the nolintlint linter with require-specific and require-explanation to enforce this automatically.

Prioritize correctness linters: govet, staticcheck, errcheck, and unused catch real bugs. Add a security linter like bodyclose or gosec for resource leaks, then style linters like revive only after correctness is covered.

Set issues.new-from-rev in .golangci.yml so only new or changed code is linted, then run golangci-lint run --fix for auto-fixable issues. Clean up remaining warnings gradually by linter category rather than mass-suppressing with //nolint.

golangci-lint v2 changed the config format, requiring a version field and a separate formatters section. Run golangci-lint migrate to convert a v1 config automatically, and check golangci-lint linters to verify linter availability in your installed version.

Never suppress security and resource linters like bodyclose, sqlclosecheck, or gosec without strong justification, since they catch real leaks and vulnerabilities. Fix errcheck on production code paths instead of suppressing, because unchecked errors cause silent failures.