mcpbeat

Go Linters

github/go-linters

Add and validate custom Go analysis linters in gh-aw.

247 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
4864
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/github/gh-aw --skill go-linters

The instruction itself

3 sections, as written by the author

Go Linters

Use this guide when adding a new custom Go analysis linter in this repository.

For PR-driven linter generation (derive a rule from a specific pull request pattern), use .github/skills/pr-to-go-linter/SKILL.md.

Where to add a new linter

  • Create a new package under pkg/linters/<linter-name>/.
  • Define an analyzer in that package (exported as Analyzer).
  • Add tests in the same package using analysistest with fixtures under testdata/src/....
  • Register the analyzer in cmd/linters/main.go so it runs via the multichecker binary.

Build and test linters

  • Test only your linter package:
  • go test ./pkg/linters/<linter-name>/...
  • Build the custom linter runner:
  • go build ./cmd/linters
  • Run all custom linters across the repo:
  • make golint-custom

make golint-custom builds cmd/linters and runs it against ./cmd/... and ./pkg/....

How to use it

Copy the folder

Take github/go-linters from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.