plugins/golang/skills/go-lint/SKILL.md
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.
npx skillsauth add openshift-eng/ai-helpers go-lintInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Run golangci-lint to check Go code quality and report issues.
Find how to run the linter using this cascade — stop at the first match:
lint or verify-lint targets (grep -E "^(lint|verify-lint):" Makefile). If found, run make lint or make verify-lint.golangci-lint run ./...Report that golangci-lint is not available and direct the user to the installation docs. Do not auto-install.
Use this format when issues are found:
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)
When clean:
Code passes all linter checks (0 issues found)
This skill is read-only. Never modify files or attempt fixes. Use the golang:lint-fix skill for that.
If the user passes additional flags, chain them to the golangci-lint invocation (e.g., --tests, --concurrency 4).
research
Shared engine for analyzing Jira issue activity and generating status summaries
testing
Snapshot OpenShift payload data (release controller, PR diffs, comments, CI jobs, JUnit results, regression tracking) to a local directory for offline analysis
development
Analyze a payload snapshot to identify root causes of blocking job failures, score candidate PRs, and produce an HTML report with revert recommendations
tools
Create TRT JIRA bugs, open revert PRs, and trigger payload jobs for high-confidence revert candidates