golang-lintLinting best practices and golangci-lint configuration for Golang projects — running linters, configuring .golangci.yml, suppressing warnings with nolint directives, interpreting lint output, and selecting linters. Use when configuring golangci-lint, asking about lint warnings or nolint suppressions, setting up code quality tooling, or choosing linters. Also use when the user mentions golangci-lint, go vet, staticcheck, or revive.
Install via ClawdBot CLI:
clawdbot install samber/golang-lintGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://github.com/samber/cc-skills-golangAudited May 23, 2026 · audit v1.0
Generated Oct 6, 2026
A platform team maintains dozens of Go microservices in a shared monorepo and needs consistent lint rules across all services. They configure a single .golangci.yml with 33+ linters and run golangci-lint in CI and pre-commit hooks. This catches style drift, unused code, and subtle bugs before merge.
An engineering team inherits a large, older Go codebase with thousands of lint warnings. Rather than fixing everything at once, they use issues.new-from-rev to lint only new code while fanning out parallel agents to clean up legacy files category by category. This makes adoption feasible without blocking feature work.
A fintech company's Go-based payment APIs must meet strict audit requirements. They enable gosec, bodyclose, and sqlclosecheck, and enforce that nolint directives include justifications. Security linters are never suppressed without documented approval, and CI fails on any new security finding.
A developer uses an AI coding agent to implement a new Go feature and the agent launches a background sub-agent running golangci-lint run --fix on modified files. The main agent continues coding while lint fixes are applied concurrently, surfacing issues when complete. This keeps code quality high without slowing down the feature implementation loop.
An open-source maintainer wants contributors to follow consistent code standards and avoid bikeshedding in PRs. They add a .golangci.yml with a curated linter set, document nolint policies in CONTRIBUTING.md, and use golangci-lint-action in GitHub Actions. Contributors get fast, consistent feedback on every pull request.
A SaaS platform provides hosted golangci-lint configurations, dashboards, and automated PR review for Go teams. It bundles lint results with analytics, trend tracking, and policy enforcement across repositories. Teams pay a monthly subscription based on the number of repositories or developers.
The core golangci-lint skill and configuration templates are free and open source, driving adoption. A paid enterprise edition adds centralized policy management, SSO, audit logs, and support SLAs for large engineering organizations. Revenue comes from enterprise licenses and premium support.
A consultancy specializes in setting up Go linting, CI pipelines, and legacy codebase cleanup engagements. They use this skill to standardize their methodology and accelerate client projects, offering fixed-price cleanup sprints and retainer-based quality assurance. Revenue is generated through project fees and ongoing retainers.
💬 Integration Tip
Install golangci-lint via the provided brew or go install command, then add a .golangci.yml from the recommended asset to your repository root and wire golangci-lint run into your CI and pre-commit hooks. For legacy projects, start with issues.new-from-rev to limit linting to new code and expand coverage gradually.
Scored Aug 21, 2026
Control desktop applications on Windows — launch, close, focus, resize, move windows, simulate keyboard/mouse input, manage processes, control VSCode, read clipboard, and capture screen info. Use when the user wants to interact with any running program, switch windows, type text, press shortcuts, open files in VSCode, manage running processes, or get system display information.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Pragmatic coding standards for writing clean, maintainable code — naming, functions, structure, anti-patterns, and pre-edit safety checks. Use when writing new code, refactoring existing code, reviewing code quality, or establishing coding standards.
Claude Code integration for OpenClaw. This skill provides interfaces to: - Query Claude Code documentation from https://code.claude.com/docs - Manage subagents and coding tasks - Execute AI-assisted coding workflows - Access best practices and common workflows Use this skill when users want to: - Get help with coding tasks - Query Claude Code documentation - Manage AI-assisted development workflows - Execute complex programming tasks
Plan, draft, version, and refine written content with enforced versioning and quality audits.
Use when writing tests, creating test strategies, or building automation frameworks. Invoke for unit tests, integration tests, E2E, coverage analysis, performance testing, security testing.