Minimizing Ty Ecosystem Changes
astral-sh/ruff
A skill your agent uses when a user says "minimize this ty ecosystem change", "reproduce this ecosystem result", "investigate a primer difference", "investigate a mypyprimer difference"…
A skill your agent uses when setting up linting for a Go project, configuring golangci-lint, or adding Go checks to a CI/CD pipeline.
Install Go Linting
$ npx skills add cxuu/golang-skills --skill go-linting -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cxuu/golang-skills go-linting --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cxuu/golang-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/go-linting .claude/skills/go-linting && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "go-linting" agent skill from https://github.com/cxuu/golang-skills/tree/main/skills/go-linting into .claude/skills/go-linting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "go-linting", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cxuu/golang-skills/tree/main/skills/go-lintingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cxuu/golang-skills --skill go-linting -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cxuu/golang-skills go-linting --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cxuu/golang-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/go-linting .agents/skills/go-linting && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "go-linting" agent skill from https://github.com/cxuu/golang-skills/tree/main/skills/go-linting into .agents/skills/go-linting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "go-linting", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cxuu/golang-skills --skill go-linting -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cxuu/golang-skills go-linting --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cxuu/golang-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/go-linting .cursor/skills/go-linting && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "go-linting" agent skill from https://github.com/cxuu/golang-skills/tree/main/skills/go-linting into .cursor/skills/go-linting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "go-linting", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cxuu/golang-skills.git --path skills/go-linting--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cxuu/golang-skills --skill go-linting -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cxuu/golang-skills go-linting --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cxuu/golang-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/go-linting .gemini/skills/go-linting && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "go-linting" agent skill from https://github.com/cxuu/golang-skills/tree/main/skills/go-linting into .gemini/skills/go-linting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "go-linting", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cxuu/golang-skills go-lintingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cxuu/golang-skills --skill go-linting -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cxuu/golang-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/go-linting .github/skills/go-linting && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "go-linting" agent skill from https://github.com/cxuu/golang-skills/tree/main/skills/go-linting into .github/skills/go-linting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "go-linting", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cxuu/golang-skills --skill go-linting -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cxuu/golang-skills go-linting --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cxuu/golang-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/go-linting .opencode/skills/go-linting && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "go-linting" agent skill from https://github.com/cxuu/golang-skills/tree/main/skills/go-linting into .opencode/skills/go-linting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "go-linting", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
go-linting- GitHub stars
- 173
- Token cost
- ~1.4k tokens
- SKILL.md length
- 496 words
- Files
- 3 (incl. scripts, assets)
- Skills in repo
- 20
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when setting up linting for a Go project, configuring golangci-lint, or adding Go checks to a CI/CD pipeline.
- Works in 4 steps: Create .golangci.yml with… → Run golangci-lint run ./... → If errors appear, fix them category by… → …
- Setting up linting for a Go project
- SKILL.md covers Core Principle, Resource Routing, Setup Procedure and Minimum Recommended Linters, plus 7 more sections
- Runs Shell scripts from its folder; calls go
What it does
Go Linting is an agent skill from cxuu/golang-skills. Use when setting up linting for a Go project, configuring golangci-lint, or adding Go checks to a CI/CD pipeline. Also use when starting a new Go project and deciding which linters to enable, even if the user only asks about "code quality" or "static analysis" without mentioning specific linter names. Does not cover code review process (see go-code-review).
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts and assets (for example `assets/golangci.yml` and `scripts/setup-lint.sh`).
It sits in Development, covering Linting and formatting. The repository describes itself as: AI Agent Skills for idiomatic, production-ready Go code, distilled from Google, Uber, Community. The licence is Apache-2.0.
When your agent uses it
- Setting up linting for a Go project
- Configuring golangci-lint
- Adding Go checks to a CI/CD pipeline
- Starting a new Go project and deciding which linters to enable
Example prompts
- “code quality”
- “static analysis”
- “/go-linting”
Requirements
- A Bash shell
- Pre-approved tools (allowed-tools): Bash(bash:*)
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Create .golangci.yml with scripts/setup-lint.sh or copy assets/golangci.yml
- Run golangci-lint run ./...
- If errors appear, fix them category by category (formatting first, then vet, then style)
- Re-run until clean
What it can do on your machine
Read from SKILL.md and the folder at commit 91f0c2e. 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(bash:*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
go
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):
github.compkg.go.devstaticcheck.dev
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 Linting loads about 1.4k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 496 words of instructions outside code blocks.
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
Auto-check passed
The automated check found no risky patterns in SKILL.md.
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); the scripts in this folder are not scanned.
SKILL.md
The full file from cxuu/golang-skills at commit 91f0c2e, republished under its Apache-2.0 licence (© cxuu). 496 words, ~1,445 tokens.
Download SKILL.mdSave it as
.claude/skills/go-linting/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- go-linting
- description
- Use when setting up linting for a Go project, configuring golangci-lint, or adding Go checks to a CI/CD pipeline. Also use when starting a new Go project and deciding which linters to enable, even if the user only asks about "code quality" or "static analysis" without mentioning specific linter names. Does not cover code review process (see go-code-review).
- allowed-tools
- Bash(bash:*)
Go Linting
Core Principle
More important than any "blessed" set of linters: lint consistently across a codebase.
Consistent linting helps catch common issues and establishes a high bar for code quality without being unnecessarily prescriptive.
Resource Routing
scripts/setup-lint.sh- Run when generating a.golangci.yml, validating the first lint pass, or producing JSON metadata.assets/golangci.yml- Use as the v2 golangci-lint baseline for established projects.
Setup Procedure
- Create
.golangci.ymlwithscripts/setup-lint.shor copyassets/golangci.yml - Run
golangci-lint run ./... - If errors appear, fix them category by category (formatting first, then vet, then style)
- Re-run until clean
After generating .golangci.yml, run golangci-lint config verify --config .golangci.yml
to verify the configuration schema before relying on lint results.
Minimum Recommended Linters
These linters catch the most common issues while maintaining a high quality bar:
| Linter | Purpose |
|---|---|
| errcheck | Ensure errors are handled |
| goimports | Format code and manage imports |
| revive | Common style mistakes (modern replacement for golint) |
| govet | Analyze code for common mistakes |
| staticcheck | Various static analysis checks |
Note:
reviveis the modern, faster successor to the now-deprecatedgolint.
Lint Runner: golangci-lint
Use golangci-lint as your lint runner. See the example .golangci.yml from uber-go/guide.
Example Configuration
Use assets/golangci.yml as the maintained example. It targets
golangci-lint v2 (verified with 2.10.1 on 2026-06-19), keeps goimports
under formatters, and enables the core linters plus common production
additions.
Running
# Install the version this skill's config is verified against
go install github.com/golangci/golangci-lint/v2/cmd/golangci-lint@v2.10.1
# Run all linters
golangci-lint run
# Run on specific paths
golangci-lint run ./pkg/...Additional Recommended Linters
Beyond the minimum set, consider these for production projects:
| Linter | Purpose | When to enable |
|---|---|---|
| gosec | Security vulnerability detection | Always for services handling user input |
| ineffassign | Detect ineffectual assignments | Always — catches dead code |
| misspell | Correct common misspellings in comments/strings | Always |
| gocyclo | Cyclomatic complexity threshold | When functions exceed ~15 complexity |
| exhaustive | Ensure switch covers all enum values | When using iota enums |
| bodyclose | Detect unclosed HTTP response bodies | Always for HTTP client code |
Show full SKILL.md (204 more words)Show less
Nolint Directives
When suppressing a lint finding, always explain why:
//nolint:errcheck // fire-and-forget logging; error is not actionable
_ = logger.Sync()Rules:
- Use
//nolint:lintername— never bare//nolint - Place the comment on the same line as the finding
- Include a justification after
//
CI/CD Integration
Run golangci-lint run ./... in CI after tests. Pin the golangci-lint version
used by CI so local and release behavior do not drift.
Pre-commit Hook
#!/bin/sh
# .git/hooks/pre-commit
golangci-lint run --new-from-rev=HEAD~1Use --new-from-rev to lint only changed code, keeping the feedback loop fast.
Quick Reference
| Task | Command/Action |
|---|---|
| Install golangci-lint | go install github.com/golangci/golangci-lint/v2/cmd/golangci-lint@v2.10.1 |
| Run linters | golangci-lint run |
| Run on path | golangci-lint run ./pkg/... |
| Config file | .golangci.yml in project root |
| CI integration | Run golangci-lint run in pipeline |
| Nolint directives | //nolint:name // reason — never bare //nolint |
| CI integration | Use golangci/golangci-lint-action for GitHub Actions |
| Pre-commit | golangci-lint run --new-from-rev=HEAD~1 |
Linter Selection Guidelines
| When you need... | Use |
|---|---|
| Error handling coverage | errcheck |
| Import formatting | goimports |
| Style consistency | revive |
| Bug detection | govet, staticcheck |
| All of the above | golangci-lint with config |
Related Skills
- Style foundations: See go-style-core when resolving style questions that linters enforce (formatting, nesting, naming)
- Code review: See go-code-review when combining linter output with a manual review checklist
- Error handling: See go-error-handling when errcheck flags unhandled errors and you need to decide how to handle them
- Testing: See go-testing when running linters alongside tests in CI pipelines
© cxuu, 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
SKILL.md and 2 other files (scripts, assets) in skills/go-linting of cxuu/golang-skills.
- SKILL.md
- assets/golangci.yml
- scripts/setup-lint.sh
Open the folder on GitHubat commit 91f0c2e
Compare with similar skills
Go Linting next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Go Linting this skillcxuu/golang-skills | 173 | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Minimizing Ty Ecosystem Changesastral-sh/ruff | 50k | — | ~4.6k | Automated safety check: Pass | MIT | |
| Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop | 5.4k | — | ~2.2k | Automated safety check: Pass | MIT | |
| Babysit PR To Pass CIsgl-project/sglang | 37k | 2 repos | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Rust Best Practicesfarm-fe/farm | 5.6k | 3 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Summarise Ecosystem Resultsastral-sh/ruff | 50k | — | ~2.2k | Automated safety check: Pass | MIT |
Similar skills
- Official
Install Anti-Slop Oxlint Rules
dmmulroy/anti-slop
Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.
Babysit PR To Pass CI
sgl-project/sglang
Start and persistently pursue a goal to babysit an SGLang pull request until selected GitHub Actions workflows pass on the latest PR head.
Rust Best Practices
farm-fe/farm
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.
- Official
Summarise Ecosystem Results
astral-sh/ruff
A skill your agent uses when a user says "summarise ecosystem results", "summarize this ty ecosystem report", "what changed in this ecosystem run?", or asks to summarise or summarize ty ecosystem…
Go Pedantry
chromedp/chromedp
This skill should be used when the user is writing Go code and needs guidance on Go-specific pedantry: error wrapping with fmt.Errorf and %w, interface design (accept interfaces return structs)…
More from cxuu/golang-skills
All 20 skills in this repoGo Testing
cxuu/golang-skills
A skill your agent uses when writing, reviewing, or improving Go test code — including table-driven tests, subtests, parallel tests, test helpers, test doubles, and assertions with cmp.Diff.
Go Code Review
cxuu/golang-skills
A skill your agent uses when reviewing Go code or checking code against community style standards.
Go Performance
cxuu/golang-skills
A skill your agent uses when optimizing Go code, investigating slow performance, or writing performance-critical sections.
Go Documentation
cxuu/golang-skills
A skill your agent uses when writing or reviewing documentation for Go packages, types, functions, or methods.
Go Error Handling
cxuu/golang-skills
A skill your agent uses when writing Go code that returns, wraps, or handles errors — choosing between sentinel errors, custom types, and fmt.Errorf (%w vs %v), structuring error flow, or deciding…
Go Interfaces
cxuu/golang-skills
A skill your agent uses when defining or implementing Go interfaces, designing abstractions, creating mockable boundaries for testing, or composing types through embedding.
Related
Categories
Questions about Go Linting
What does Go Linting do?
A skill your agent uses when setting up linting for a Go project, configuring golangci-lint, or adding Go checks to a CI/CD pipeline. Go Linting is an agent skill from cxuu/golang-skills. Use when setting up linting for a Go project, configuring golangci-lint, or adding Go checks to a CI/CD pipeline.
When should I use Go Linting?
Go Linting fits situations like: setting up linting for a Go project; configuring golangci-lint; adding Go checks to a CI/CD pipeline; starting a new Go project and deciding which linters to enable.
How do I install Go Linting in Claude Code?
Run `npx skills add cxuu/golang-skills --skill go-linting -a claude-code`. Or copy the skill folder (skills/go-linting in cxuu/golang-skills) into .claude/skills/go-linting in your project. Claude Code loads it when a task matches its description.
How do I install Go Linting in Codex?
Run `npx skills add cxuu/golang-skills --skill go-linting -a codex`. Or copy the skill folder (skills/go-linting in cxuu/golang-skills) into .agents/skills/go-linting in your project. Codex loads it when a task matches its description.
Can I use Go Linting in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cxuu/golang-skills --skill go-linting -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/go-linting, .gemini/skills/go-linting, .github/skills/go-linting and .opencode/skills/go-linting in your project.
What does Go Linting need to run?
Going by SKILL.md and its folder, Go Linting needs a shell for the scripts in its folder and the command-line tools its instructions call (go). Our summary lists: A Bash shell. Its frontmatter pre-approves these tools: Bash(bash:*).
Does Go Linting access the network?
SKILL.md names 3 domains. As links in the text: github.com, pkg.go.dev and staticcheck.dev. This is read from the text; nothing was executed.
Is Go Linting safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Go Linting use?
Go Linting is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Go Linting use?
About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Go Linting?
Skills that share tags, products or a category with Go Linting: Minimizing Ty Ecosystem Changes (astral-sh/ruff, 50k stars), Install Anti-Slop Oxlint Rules (dmmulroy/anti-slop, 5.4k stars), Babysit PR To Pass CI (sgl-project/sglang, 37k stars) and Rust Best Practices (farm-fe/farm, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Go Linting?
cxuu (a GitHub user) maintains it in cxuu/golang-skills, which has 173 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on June 20, 2026.
Source: cxuu/golang-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.