Configure and run golangci-lint v2 with justified //nolint suppressions.
npx skills add https://github.com/dmwin72015/netdisk --skill golang-lint-dmwin72015
Please help me install this Agent Skill. Skill: golang-lint Source: https://github.com/dmwin72015/netdisk/tree/main/.agents/skills/golang-lint Command: npx skills add https://github.com/dmwin72015/netdisk --skill golang-lint-dmwin72015
This Skill helps Go teams reduce bugs and quality regressions by standardizing how golangci-lint is configured, run, and interpreted, especially when deciding whether to fix issues or suppress false positives.
.golangci.yml (version v2), enable/disable the right linters, and tune settings for your codebase.golangci-lint run --fix, while you continue implementing features.//nolint:<linter> // reason suppressions correctly and safely.Configure your Go project’s .golangci.yml using the recommended linters and settings, then run lint with auto-fixes and explain any remaining findings so you can fix or suppress them with justified //nolint directives.
High-intent search queries and answers about installing and using this skill.
You configure golangci-lint by generating a `.golangci.yml` file using the v2 configuration structure, enabling appropriate linters, and tuning settings to match your Go codebase for reliable code quality.
You suppress golangci-lint warnings safely by applying `//nolint:<linter> // reason` directives, ensuring you include the specific linter name and a justification to avoid masking real code quality issues.
Auto-fix linting errors in Go files by running `golangci-lint run --fix` on changed files, automatically resolving safe issues while you continue implementing features and addressing remaining findings manually.
Yes, you need both the `go` environment and the `golangci-lint` tool installed to run static analysis, interpret linter-tagged output, and apply justified `//nolint` suppressions for your codebase.
Interpret golangci-lint output by reading the linter name tagged in each finding, then triage whether to fix the underlying cause directly or apply a justified `//nolint` suppression for false positives.
Use `//nolint` instead of refactoring when a lint warning is a false positive or when fixing it risks breaking functionality, ensuring you always document the specific linter name and a clear rationale.
dotBeepsRun go vet, golangci-lint, and go test on Go code.
Utchash007Identify and fix lint warnings in Go projects using golangci-lint.
carayaAutomate Go code formatting with gofmt, goimports, and golangci-lint.
Harmeet10000Configure v2 golangci-lint with recommended linters and nolint directives.