go-linting
Use when setting up linting, configuring golangci-lint, or fixing linter warnings in Go projects. Provides recommended linter sets, golangci-lint configuration, CI integration, and Makefile targets.
Best use case
go-linting is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when setting up linting, configuring golangci-lint, or fixing linter warnings in Go projects. Provides recommended linter sets, golangci-lint configuration, CI integration, and Makefile targets.
Teams using go-linting should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/go-linting/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How go-linting Compares
| Feature / Agent | go-linting | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when setting up linting, configuring golangci-lint, or fixing linter warnings in Go projects. Provides recommended linter sets, golangci-lint configuration, CI integration, and Makefile targets.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Go Linting
Recommended linters and configuration for Go projects.
## golangci-lint Setup
golangci-lint is the standard linter aggregator for Go. Install it as a tool dependency in your module:
```bash
# Add to go.mod (Go 1.24+)
go get -tool github.com/golangci/golangci-lint/cmd/golangci-lint
# Or install directly
go install github.com/golangci/golangci-lint/cmd/golangci-lint@latest
```
## Recommended Configuration
Place `.golangci.yml` at the project root. This uses the golangci-lint v2 config format:
```yaml
version: "2"
run:
timeout: 5m
go: "1.25"
linters:
enable:
- errcheck # unchecked errors
- govet # go vet checks
- staticcheck # comprehensive static analysis (includes gosimple)
- revive # flexible linter, replaces golint
- ineffassign # unused assignments
- unused # unused code
- misspell # spelling in comments and strings
- unconvert # unnecessary type conversions
- gocritic # opinionated style and performance checks
- errname # error naming conventions (Err prefix)
- errorlint # error wrapping patterns
- copyloopvar # loop variable copy issues (pre-Go 1.22)
- nilerr # returning nil when err is not nil
- bodyclose # unclosed HTTP response bodies
- prealloc # slice preallocation
settings:
revive:
rules:
- name: exported
arguments:
- "checkPrivateReceivers"
- name: blank-imports
- name: context-as-argument
- name: context-keys-type
- name: error-return
- name: error-strings
- name: error-naming
- name: increment-decrement
- name: var-naming
- name: package-comments
- name: range
- name: receiver-naming
- name: indent-error-flow
- name: empty-block
- name: superfluous-else
- name: unreachable-code
- name: redefines-builtin-id
gocritic:
enabled-tags:
- diagnostic
- style
- performance
errcheck:
check-type-assertions: true
check-blank: true
govet:
enable-all: true
exclusions:
rules:
# Allow unused parameters in interface implementations
- linters:
- revive
text: "unused-parameter"
# Test files can use dot imports
- path: _test\.go
linters:
- revive
text: "dot-imports"
formatters:
enable:
- goimports # import formatting and grouping
settings:
goimports:
local-prefixes:
- yourcompany.com
issues:
max-issues-per-linter: 0
max-same-issues: 0
```
Update `local-prefixes` under `formatters.settings.goimports` to match your module path.
Note: this config uses golangci-lint v2 format (`version: "2"`). If you are on golangci-lint v1, run `golangci-lint migrate` to convert, or remove the `version` line and move `formatters` back into `linters`.
## Makefile Integration
```makefile
.PHONY: lint lint-fix
lint: ## Run linters
go tool golangci-lint run ./...
lint-fix: ## Run linters with auto-fix
go tool golangci-lint run --fix ./...
```
If golangci-lint is not a tool dependency:
```makefile
lint:
golangci-lint run ./...
```
## CI Integration
### GitHub Actions
```yaml
name: lint
on: [push, pull_request]
jobs:
golangci-lint:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-go@v5
with:
go-version: "1.25"
- uses: golangci/golangci-lint-action@v6
with:
version: latest
```
## Per-Linter Guidance
### errcheck
Finds unchecked errors. Fix by handling or explicitly ignoring:
```go
// Wrong: error ignored silently
json.Unmarshal(data, &v)
// Correct: handle the error
if err := json.Unmarshal(data, &v); err != nil {
return fmt.Errorf("unmarshal config: %w", err)
}
```
### errorlint
Enforces proper error wrapping and comparison:
```go
// errorlint flags this: use errors.Is instead
if err == ErrNotFound { }
// Correct
if errors.Is(err, ErrNotFound) { }
```
### bodyclose
Catches unclosed HTTP response bodies:
```go
resp, err := http.Get(url)
if err != nil {
return err
}
defer resp.Body.Close() // bodyclose checks for this
```
### govet
Runs the same checks as `go vet` plus additional analyzers. Key checks:
- **printf**: format string / argument mismatch
- **shadow**: variable shadowing
- **structtag**: malformed struct tags
- **copylocks**: passing locks by value
## Suppressing False Positives
```go
//nolint:errcheck // intentionally ignoring close error on read-only file
_ = f.Close()
//nolint:gocritic // hugeParam: passing by value is intentional here
func process(cfg Config) { }
```
Use `//nolint` comments sparingly. Prefer fixing the issue over suppressing it.Related Skills
go-testing
Use when writing, reviewing, or debugging Go tests and benchmarks. Covers table-driven tests, parallel execution, go-cmp, T.Context, T.Chdir, b.Loop, synctest for deterministic concurrency testing, and test failure messages.
go-security
Use when writing, reviewing, or auditing Go code for security. Covers input validation, SQL injection prevention, path traversal, secrets management, cryptography, HTTP security headers, and dependency scanning.
go-project-layout
Use when starting a new Go project, organizing packages, or restructuring an existing Go codebase. Covers standard directory layout, package design, Makefile targets, Dockerfile patterns, and module setup.
go-performance
Use when writing, reviewing, or optimizing Go code for performance. Covers string operations, memory allocation, preallocating slices and maps, strings.Builder, strconv, container-aware GOMAXPROCS, and runtime considerations for Go 1.25.
go-error-handling
Use when writing, reviewing, or debugging Go error handling code. Covers error wrapping, sentinel errors, custom error types, error joining, single handling, and error flow patterns. Based on Google and Uber style guides.
go-concurrency
Use when writing, reviewing, or debugging concurrent Go code. Covers goroutine lifecycle management, channels, errgroup, mutexes, atomics, sync.Map, and synchronous-first design. Based on Google and Uber style guides.
go-code-review
Use when reviewing Go code or preparing code for review. Quick-reference checklist covering naming, error handling, concurrency, testing, imports, documentation, and common pitfalls. Based on Go Wiki CodeReviewComments.
golang
Use when writing, reviewing, or refactoring Go code. Provides production best practices for Go covering error handling, concurrency, naming, testing, performance, generics, iterators, and common pitfalls. Distilled from Google Go Style Guide, Uber Go Style Guide, Effective Go, and Go Code Review Comments. Updated for Go 1.25.
code-linting
Run linters according to repository guidelines. Use immediately after creating or modifying code, or before committing changes.
linting-neostandard-eslint9
Configures ESLint v9 flat config and neostandard for JavaScript and TypeScript projects, including migrating from legacy `.eslintrc*` files or the `standard` package. Use when you need to set up or fix linting with `eslint.config.js` or `eslint.config.mjs`, troubleshoot lint errors, configure neostandard rules, migrate from `.eslintrc` to flat config, or integrate linting into CI pipelines and pre-commit hooks.
swe-cli-skills
Senior engineer CLI expertise for AI agents — workflows, safety guardrails, gotchas, and anti-patterns across cloud, IaC, containers, databases, dev tools, and platforms
PicoClaw Fleet
Orchestrate a fleet of remote PicoClaw workers over SSH for fast, ephemeral one-shot tasks.