How do I install the Golang Tooling skill?

Run npx skillmds@latest add comeonoliver/golang-tooling in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Golang Tooling safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Golang Tooling?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Golang Tooling free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Golang Tooling?

ComeOnOliver (@comeonoliver) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Golang Tooling by comeonoliver — Agent Skill

Name: Golang Tooling
Rating: 4.2 (5 reviews)
Author: ComeOnOliver

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)

ComeOnOliver Updated Sep 8, 2026 61 repo stars

File contents

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 does formatting AND imports.
No manual import sorting: Let goimports manage the order.
No skipping go vet: Run it — catches real bugs gofmt misses.
No broad lint disable: Fix the root cause instead of //nolint comments.

References

golangci.yml example

---name: golang-toolingdescription: 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)---# Golang Tooling Standards## **Priority: P1 (Operational)**## Verification Workflow (Mandatory)After writing or modifying Go code, run in order:1. **`mcp__ide__getDiagnostics`** — gopls real-time errors and type warnings (requires gopls-lsp plugin)2. **`go vet ./...`** — catch printf mismatches, unreachable code, shadowed variables3. **`goimports -w .`** — organize imports and format in one pass4. **`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 SetupConfigure 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 issuesSee [golangci.yml example](references/golangci.md).## gopls Integration`gopls` powers `mcp__ide__getDiagnostics`. Install:```bashgo install golang.org/x/tools/gopls@latest```## Anti-Patterns- **No `gofmt` alone**: Use `goimports` — it does formatting AND imports.- **No manual import sorting**: Let `goimports` manage the order.- **No skipping go vet**: Run it — catches real bugs `gofmt` misses.- **No broad lint disable**: Fix the root cause instead of `//nolint` comments.## References- [golangci.yml example](references/golangci.md)

Frequently asked questions