What problem does it solve? Go projects accumulate lint warnings without a consistent configuration, and developers often suppress warnings incorrectly with bare //nolint directives or disable valuable linters. This Skill provides a production-ready golangci-lint v2 configuration, clear rules for when to fix versus suppress warnings, and workflows for adopting linting on legacy codebases. ## Core Features & Use Cases - Recommended Configuration: Ships a .golangci.yml with 48 linters organized by domain (correctness, style, complexity, performance, security, testing) plus explicit disable rationales for noisy linters. - Nolint Hygiene: Enforces specific, justified //nolint directives via the nolintlint meta-linter, with patterns for single-line, multi-linter, and per-function suppression. - Legacy Adoption: Uses issues.new-from-rev to lint only new code and parallel sub-agents to clean up existing warnings by category. - Use Case: A team inheriting a Go monorepo with 2000+ lint warnings can apply the recommended config, set new-from-rev to stop the bleeding on new code, and batch-fix security and error-handling findings first. ## Quick Start Ask the agent to set up golangci-lint for your Go project using the recommended configuration and run it on your codebase.
