linter-runner
Installation
SKILL.md
Linter Runner
When to Use
- After formatting and before/after tests or PR creation to ensure linter parity with CI.
Rules
- Use the repository's configured linter commands (see
AGENTS.md). - Prioritize actionable issues: security/correctness > concurrency > API misuse > style.
- Provide minimal code-change suggestions; avoid large refactors unless explicitly requested.
Commands
- Primary:
golangci-lint run --timeout 5m --verbose ./...(CI uses golangci-lint v2.8.0) - Secondary:
revive ./...
Output
- Top findings (5-15) grouped by file and rule.
- One-line fix suggestion per finding.
- Verification steps (re-run lint, run focused tests).
Related Skills
code-formatter,static-analysis,test-runner
Related skills
More from pilinux/gorest
file-reader
Precisely read source files or snippets and return concise, citation-backed facts needed for decisions or edits.
27code-navigation
Rapid, focused navigation to locate definitions/usages and map the impact of proposed changes.
7fix-suggester
Diagnose failures and propose minimal, test-backed fixes with verification and rollback instructions.
7build-run
Build and run the project locally to reproduce compile/runtime issues in a safe, non-production way.
7logs-repro-harness
Reduce flaky or environment-dependent failures to a minimal, reproducible script and capture the exact logs and error lines.
7ci-orchestrator
Run a CI-like pipeline locally (format, lint, vet, static-analysis, tests) and summarize per-step results with remediation guidance.
6