golang-code-styleGolang code style conventions — line length and breaking, variable declarations, control flow clarity, when comments help vs hurt. Use when writing or reviewing Go code, asking about style or clarity, or establishing project coding standards. Not for naming conventions (→ See `samber/cc-skills-golang@golang-naming` skill), linter configuration (→ See `samber/cc-skills-golang@golang-lint` skill), or doc comments (→ See `samber/cc-skills-golang@golang-documentation` skill).
Install via ClawdBot CLI:
clawdbot install samber/golang-code-styleGrade 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 Apr 17, 2026 · audit v1.0
Generated May 5, 2026
Teams new to Go or adopting a new Go codebase can use this skill to enforce consistent formatting, variable declarations, and control flow patterns. It reduces onboarding friction by providing clear style rules that complement linters, ensuring all developers write maintainable, idiomatic Go code from day one.
In code review pipelines, this skill can be invoked to automatically flag style issues like line breaking at semantic boundaries, unnecessary else clauses, and nil slice/map initialization. It augments human reviewers by catching subjective style violations that linters miss, speeding up reviews and improving code quality.
When setting up linting tools like golangci-lint or writing project-specific style guides, this skill provides the rationale behind rules such as composite literal field names and default-then-override patterns. It helps teams configure linters to align with human-readable conventions, avoiding arbitrary or excessive warnings.
Teams refactoring large Go monoliths can apply this skill to systematically reduce nesting, break long function signatures, and initialize slices/maps consistently. It guides incremental improvements that make code easier to test, debug, and extend without breaking existing functionality.
Go training courses and bootcamps can embed this skill as a reference for best practices, teaching learners how to structure functions, handle errors with early returns, and use switch statements over if-else chains. It serves as a living style guide that evolves with the language and the team's experience.
Integrate this skill into an AI-powered code review or pair programming tool that charges per-seat or per-repo. The skill adds value by enforcing nuanced Go style rules that go beyond linters, justifying a premium tier for teams wanting consistent, idiomatic Go code.
Offer consulting services to assess and improve Go codebases, using this skill as a framework for style audits. Deliverables include prioritized refactoring recommendations, automated style checks, and team training, billed at hourly or project rates.
Enterprise development experience platforms (e.g., GitHub, GitLab) can license or bundle this skill into their workflow automation and code review features. It enhances the platform's ability to enforce custom style rules, driving adoption and stickiness among Go-using teams.
💬 Integration Tip
To integrate, clone the skill repository into your agent's skill directory and ensure the 'go' binary is in PATH. The skill works best when combined with the companion naming and design patterns skills.
Scored Sep 25, 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.