golang-error-handlingIdiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single handling rule, structured logging with slog, HTTP request logging middleware, and samber/oops for production errors. Built to make logs usable at scale with log aggregation 3rd-party tools. Apply when creating, wrapping, inspecting, or logging errors in Go code. For samber/oops specifics → See `samber/cc-skills-golang@golang-samber-oops` skill; for slog handler ecosystem → See `samber/cc-skills-golang@golang-samber-slog` skill.
Install via ClawdBot CLI:
clawdbot install samber/golang-error-handlingGrade 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 Oct 6, 2026
A fintech team building a Go payment gateway needs every transaction failure to be traceable across microservices. Using this skill, they wrap errors with %w at each layer, attach tenant and transaction IDs via samber/oops, and enforce the single handling rule so logs aren't duplicated in their aggregation pipeline.
A platform engineering group audits a large Kubernetes operator codebase for swallowed errors and log-and-return pairs before a production rollout. They fan out the five parallel sub-agents across creation, wrapping, single-handling, panic/recover, and structured logging categories to consolidate findings into a prioritized remediation list.
An e-commerce backend handles order creation, inventory reservation, and shipping callbacks in Go. The team adopts slog middleware to log HTTP requests with method, path, status, and duration, and uses errors.AsType to classify downstream failures into user-friendly messages while logging technical details internally.
A healthcare SaaS provider must keep audit logs low-cardinality for aggregation while retaining patient context in structured attributes. They use sentinel errors for expected validation failures and custom error types carrying patient and request identifiers, ensuring no PHI leaks into stable log messages.
A B2B SaaS company struggles with noisy alerts from duplicated error logs across tenants. Adopting the single handling rule and samber/oops for stack traces and tenant context, they reduce alert fatigue and cut mean time to resolution during incidents.
Maintainers of Go libraries and frameworks adopt the skill as a community standard to produce consistent, idiomatic error handling in upstream projects, driving adoption and ecosystem credibility.
A platform team codifies this skill into internal golden paths, CI lint rules, and PR review checklists so all Go services follow uniform error handling and logging conventions.
Training providers package the skill's best practices into Go reliability courses and certification programs aimed at backend engineers and SREs preparing for production-grade work.
💬 Integration Tip
Enable this skill for all **/*.go paths and ensure the go binary and golangci-lint are available so audit and review modes can run; pair it with samber/oops and samber-slog companion skills for full production error and logging coverage.
Scored Oct 6, 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.