Agent-skills-standard golang-tooling

Go developer toolchain — gopls LSP diagnostics, linting, formatting, and vet. Use when setting up Go tooling, running linters, or integrating gopls with Claude Code. (triggers: gopls, golangci-lint, golangci.yml, go vet, goimports, staticcheck, go tooling, go lint)

install

source · Clone the upstream repo

git clone https://github.com/HoangNguyen0403/agent-skills-standard

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/HoangNguyen0403/agent-skills-standard "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/golang/golang-tooling" ~/.claude/skills/hoangnguyen0403-agent-skills-standard-golang-tooling && rm -rf "$T"

manifest: skills/golang/golang-tooling/SKILL.md

source content

Golang Tooling Standards

Priority: P1 (Operational)

Verification Workflow (Mandatory)

After writing or modifying Go code, run in order:

mcp__ide__getDiagnostics
— gopls real-time errors and type warnings (requires gopls-lsp plugin)
go vet ./...
— catch printf mismatches, unreachable code, shadowed variables
goimports -w .
— organize imports and format in one pass
golangci-lint run ./...
— run full linter suite (if
```
.golangci.yml
```
present)

Tool Overview

Tool	Purpose	When to Use
`gopls`	LSP: diagnostics, completion, hover	Always (IDE integration)
`go vet`	Static analysis — correctness bugs	After every edit
`goimports`	Import sorting + `gofmt`	Before commit
`golangci-lint`	Aggregated linters (errcheck, staticcheck, etc.)	CI / pre-commit
`staticcheck`	Advanced static analysis	Large codebases

golangci-lint Setup

Configure via

.golangci.yml

at repo root. Recommended linters:

```
errcheck
```
— enforce error handling
```
staticcheck
```
— bug detection beyond go vet
```
govet
```
— shadow, composites
```
revive
```
— style enforcement
```
gosec
```
— security issues

See golangci.yml example.

gopls Integration

gopls

powers

mcp__ide__getDiagnostics

. Install:

go install golang.org/x/tools/gopls@latest

Anti-Patterns

No
gofmt
alone: Use
```
goimports
```
— it formatting AND imports.
No manual import sorting: Let
```
goimports
```
manage order.
No skipping go vet: Run it — catches real bugs
```
gofmt
```
misses.
No broad lint disable: Fix root cause instead of
```
//nolint
```
comments.

References

golangci.yml example