Go Lint

What it does

When your agent uses it

• The user asks to lint
• Check for lint issues
• Verify code quality in a Go project
• Linting is appropriate before committing Go code changes

Example prompts

• “/go-lint”

Requirements

• Pre-approved tools (allowed-tools): Bash(golangci-lint *), Bash(grep *), Bash(make lint), Bash(make verify-lint), Read

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

1. 1CLAUDE.md / AGENTS.md: Check for instructions about linting. If a lint command is documented, use it.
2. 2Makefile targets: Check for lint or verify-lint targets (grep -E "^(lint|verify-lint):" Makefile). If found, run make lint or make…
3. 3Direct invocation: Run golangci-lint run ./...

What it can do on your machine

Read from SKILL.md and the folder at commit a627176. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • Bash(golangci-lint *)
  • Bash(grep *)
  • Bash(make lint)
  • Bash(make verify-lint)
  • Read

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • make

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  Links to these hosts (documentation or services it may open):

  • golangci-lint.run

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Go Lint loads about 439 tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 135 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~53

When it runs · the whole SKILL.md, loaded when a task matches

~439

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from openshift-eng/ai-helpers at commit a627176, republished under its Apache-2.0 licence (© openshift-eng). 135 words, ~439 tokens.

name

go-lint

description

Run golangci-lint to check Go code quality. Use when the user asks to lint, check for lint issues, or verify code quality in a Go project, or when linting is appropriate before committing Go code changes.

allowed-tools

Bash(golangci-lint *), Bash(grep *), Bash(make lint), Bash(make verify-lint), Read

model

haiku

paths

**/*.go, .golangci.yml, .golangci.yaml

Found 15 issues:
- goconst: 5 issues
- staticcheck: 4 issues
- gocyclo: 3 issues
- revive: 3 issues

Example issues:
- pkg/api/handler.go:42: string "application/json" has 3 occurrences (goconst)
- pkg/utils/helper.go:87: cyclomatic complexity 15 of function ProcessData (gocyclo)

Code passes all linter checks (0 issues found)

© openshift-eng, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/golang/skills/go-lint of openshift-eng/ai-helpers.

Open the folder on GitHubat commit a627176