More important than any "blessed" set of linters: lint consistently across a codebase.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongo-lintingExecute the skills CLI command in your project's root directory to begin installation:
Fetches go-linting from cxuu/golang-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate go-linting. Access via /go-linting in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
65
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
65
stars
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.
.golangci.yml using the configuration belowgolangci-lint run ./...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.
Use golangci-lint as your lint runner. See the example .golangci.yml from uber-go/guide.
See
assets/golangci.ymlwhen creating a new.golangci.ymlor comparing your existing config against a recommended baseline.
Create .golangci.yml in your project root:
linters:
enable:
- errcheck
- goimports
- revive
- govet
- staticcheck
linters-settings:
goimports:
local-prefixes: github.com/your-org/your-repo
revive:
rules:
- name: blank-imports
- name: context-as-argument
- name: error-return
- name: error-strings
- name: exported
run:
timeout: 5m
# Install
go install github.com/golangci/golangci-lint/cmd/golangci-lint@latest
# Run all linters
golangci-lint run
# Run on specific paths
golangci-lint run ./pkg/...
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 |
When suppressing a lint finding, always explain why:
//nolint:errcheck // fire-and-forget logging; error is not actionable
_ = logger.Sync()
Rules:
//nolint:lintername — never bare //nolint//# .github/workflows/lint.yml
name: Lint
on: [push, pull_request]
jobs:
lint:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-go@v5
with:
go-version: stable
- uses: golangci/golangci-lint-action@v6
with:
version: latest
#!/bin/sh
# .git/hooks/pre-commit
golangci-lint run --new-from-rev=HEAD~1
Use --new-from-rev to lint only changed code, keeping the feedback loop fast.
scripts/setup-lint.sh — Generates .golangci.yml and runs initial lintbash scripts/setup-lint.sh github.com/your-org/your-repo
bash scripts/setup-lint.sh --force github.com/your-org/your-repo # overwrite existing
bash scripts/setup-lint.sh --dry-run # preview config
bash scripts/setup-lint.sh --json # structured output
Validation: After generating
.golangci.yml, rungolangci-lint run ./...to verify the configuration is valid and produces expected output. If it fails with a config error, fix and retry.
scripts/setup-lint.shgenerates a minimum config (5 core linters). For established projects, useassets/golangci.ymlas a starting point — it adds gosec, ineffassign, misspell, gocyclo, and bodyclose.
| Task | Command/Action |
|---|---|
| Install golangci-lint | go install github.com/golangci/golangci-lint/cmd/golangci-lint@latest |
| 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 |
| 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 |
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
jwynia/agent-skills
mindrally/skills
github/awesome-copilot
kostja94/marketing-skills
wispbit-ai/skills
shubhamsaboo/awesome-llm-apps
Useful defaults in go-linting — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
go-linting fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
go-linting has been reliable in day-to-day use. Documentation quality is above average for community skills.
go-linting is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
go-linting fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
go-linting is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: go-linting is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added go-linting from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
go-linting reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for go-linting matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 43