Golang Linter
v1.1.1Provides linting best practices and golangci-lint configuration for Go projects. Covers running linters, configuring .golangci.yml, suppressing warnings with...
⭐ 0· 96·0 current·0 all-time
bySamuel Berthe@samber
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description (golang linter + golangci-lint configuration) match required binaries (go, golangci-lint) and the brew install. There are no environment variables, unrelated binaries, or credentials requested — everything requested is proportional to the stated purpose.
Instruction Scope
SKILL.md stays within linting scope (configuring .golangci.yml, interpreting output, nolint guidance). Two noteworthy items: (1) it refers to a recommended assets/.golangci.yml but that file is not present in the manifest — the skill may assume an asset that won't be available. (2) The instructions explicitly recommend launching background/sub-agents to run `golangci-lint run --fix` and to perform parallel autofixes; that is coherent for an automated linting workflow but means the skill will autonomously modify repository files unless the agent/operator constrains it. This behavior is expected for a linting assistant but could be surprising if you don't want automated edits.
Install Mechanism
Install uses a Homebrew formula for golangci-lint (well-known distribution channel). No downloads from untrusted URLs or archive extraction are present. This is a low-risk, proportional install mechanism for this tool.
Credentials
The skill requires no environment variables, credentials, or config paths. No secrets are requested and none of the declared requirements are excessive relative to the linting purpose.
Persistence & Privilege
always:false and no special system-wide configuration changes are requested. However, the skill encourages autonomous use of sub-agents and automated --fix runs which can change code. Autonomous invocation is platform-default and not inherently problematic, but combined with automatic code modification it may be surprising; consider restricting autonomous execution or requiring user confirmation for fixes.
Assessment
This skill is internally consistent for a golangci-lint helper: it only needs go and golangci-lint and installs via Homebrew. Before installing, consider: 1) The SKILL.md references a recommended assets/.golangci.yml that is not included — verify or supply your own .golangci.yml before running. 2) The skill suggests running `golangci-lint --fix` and spawning parallel sub-agents to apply fixes automatically; if you do not want automated edits, disable autonomous invocation or require manual confirmation for fixes and run linting in a dry-run first (e.g., run without --fix or review changes in a branch/PR). 3) Ensure Homebrew installation is acceptable on your environment. 4) As with any tool that modifies code, run it on a feature branch, have CI/tests, and review generated changes before merging.Like a lobster shell, security has layers — review code before you run it.
latestvk97dd86wsr4f4nhv3wt99t8kq983qesk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🧹 Clawdis
Binsgo, golangci-lint
Install
Homebrew
Bins: golangci-lint
brew install golangci-lint