Golang Tooling

Name: Golang Tooling
Author: HoangNguyen0403

ASecurity

Go developer toolchain — gopls LSP diagnostics, linting, formatting, and vet. Use when setting up Go tooling, running linters, or integrating gopls with Claude Code.

549 stars
0 votes
0 copies
1 view
Added June 6, 2026

developmentgobashsecurity

Works with

claude code
mcp

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned June 6, 2026

npx -y skills add HoangNguyen0403/agent-skills-standard --skill golang-tooling --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Golang Tooling?

Add the live security badge to your README. It updates with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/hoangnguyen0403-golang-tooling/badge)](https://www.skillsdirectory.com/skills/hoangnguyen0403-golang-tooling)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: golang-tooling
description: Go developer toolchain — gopls LSP diagnostics, linting, formatting, and vet. Use when setting up Go tooling, running linters, or integrating gopls with Claude Code.
metadata:
  triggers:
    files:
    - 'golangci.yml'
    keywords:
    - gopls
    - golangci-lint
    - 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 variables
3. **`goimports -w .`** — organize imports and format in one pass
4. **`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](references/golangci.md).

## gopls Integration

`gopls` powers `mcp__ide__getDiagnostics`. Install:

```bash
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](references/golangci.md)