/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.
$ npx -y skills add hoangnguyen0403/agent-skills-standard --skill golang-tooling --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/golang-tooling
Context preview
The summary Claude sees to decide when to auto-load this skill.
Go developer toolchain — gopls LSP diagnostics, linting, formatting, and vet. Use when setting up Go tooling, running linters, or integrating gopls with Claude Code.
SKILL.md
golang-tooling.SKILL.mdname: 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 lintGolang Tooling Standards
**Priority: P1 (HIGH)**
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:
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)
Read more
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 lintGolang Tooling Standards
**Priority: P1 (HIGH)**
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:
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)
The portable SDLC standards layer for AI coding agents. Sync once, then work in your own runtime.
Repo: hoangnguyen0403/agent-skills-standard
Other skills on agent-skills-standard.
- /android-agp-upgrade
Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.
Open skill - /android-architecture
Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow
Open skill - /android-background-work
Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers; defer FCM and notification delivery to android-notifications.
Open skill - /android-compose-migration
Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.
Open skill - /android-compose
Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.
Open skill - /android-concurrency
Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes,
Open skill

