Configure and run golangci-lint quality gates for Go codebases.
npx skills add https://github.com/asarchami/dotfiles --skill go-lint-asarchami
Please help me install this Agent Skill. Skill: go-lint Source: https://github.com/asarchami/dotfiles/tree/main/dot_config/opencode/skills/go/go-lint Command: npx skills add https://github.com/asarchami/dotfiles --skill go-lint-asarchami
.golangci.yml with 33+ enabled linters organized by domain (correctness, style, complexity, performance, security, testing), each with documented rationale. - Quality gate pipeline: Wires gofmt, go vet, go test with race and coverage, golangci-lint, gosec, and govulncheck into a single local and CI gate with concrete metric targets (coverage ≥80%, complexity ≤10, zero gosec findings). - nolint discipline and PR review framework: Enforces justified, linter-specific suppressions via nolintlint and organizes review feedback into Critical, Important, Suggestion, and Positive buckets. - Use Case: When inheriting a legacy Go repository, apply issues.new-from-rev: HEAD~1 so only new code is gated, then parallelize cleanup across linter categories until the full gate passes. ## Quick Start Set up a golangci-lint quality gate for my Go repository using the recommended configuration and show me how to run it locally.High-intent search queries and answers about installing and using this skill.
Create a .golangci.yml file at the repo root with version "2", enable linters by domain (correctness, style, complexity, security, testing), and run golangci-lint run ./... locally and in CI. Start from a curated config with documented rationale for each linter.
Set issues.new-from-rev to HEAD~1 in .golangci.yml so only changed lines are gated. This prevents existing lint debt from blocking new diffs while you track and clean up the backlog separately.
Enable linters across domains: govet, staticcheck, errcheck for correctness; gocritic and revive for style; gocyclo and funlen for complexity; gosec, bodyclose, sqlclosecheck for security; thelper and testifylint for tests. Disable noisy ones like mnd and varnamelen.
Suppress only after confirming a false positive or intentional pattern, always naming the specific linter and adding a justification comment. Never blanket-suppress security linters like bodyclose or sqlclosecheck; the nolintlint linter enforces both rules.
The default analysis timeout is 5 minutes, which large repos can exceed. Raise run.timeout in .golangci.yml, or reduce run.concurrency and add run.skip-dirs to speed up analysis on big codebases.
Run golangci-lint migrate to convert a v1 configuration to the v2 format automatically. The v2 config requires version: "2" at the top and restructures some settings sections.
marsolabWrite idiomatic Go code with structured error handling and linting guidance.
pko89403Automate GitHub Actions CI/CD pipelines with linting, type checks, tests, and builds.
erigontechRuns Erigon Go test suites with the race detector to find data races and concurrency bugs.
ozan-fnRun golangci-lint and manage .golangci.yml configurations for Go code.