What problem does it solve? Go projects accumulate lint warnings, inconsistent formatting, and unchecked errors when linting is not configured as a first-class workflow step. This Skill provides a production-ready golangci-lint v2 configuration, guidance on interpreting lint output, and rules for when to fix versus suppress warnings. ## Core Features & Use Cases - Configuration Setup: Provides a recommended .golangci.yml with 48 linters organized by domain (correctness, style, complexity, performance, security, testing) plus per-linter settings and documented disable rationales. - Warning Suppression Discipline: Enforces //nolint:linter // justification syntax, comma-separated multi-linter suppression, and the nolintlint meta-linter to prevent bare suppressions. - Legacy Codebase Adoption: Uses issues.new-from-rev for incremental linting and parallel sub-agents to clean up large backlogs by linter category. - Use Case: A team adopting golangci-lint on a legacy monorepo with 2000+ warnings can lint only new code, auto-fix with --fix, and triage remaining issues by category without drowning in noise. ## Quick Start Ask the agent to set up golangci-lint for your Go project with a recommended .golangci.yml and run it on the codebase.