Review Go error handling for panic usage, wrapping, and error checks.
npx skills add https://github.com/v0lka/skills --skill go-error-management
Please help me install this Agent Skill. Skill: go-error-management Source: https://github.com/v0lka/skills/tree/main/development/idiomatic-go/go-error-management Command: npx skills add https://github.com/v0lka/skills --skill go-error-management
Go projects often suffer from brittle error handling due to misused panics, improper wrapping or transforming of errors, and inconsistent checks with errors.Is and errors.As. This skill guides developers to write robust, maintainable error-handling code by clarifying when to panic, how to wrap vs transform errors, how to inspect errors reliably, ensure errors are handled exactly once, avoid silent ignores, and handle defer-related errors safely.
Audit an existing Go function and rewrite its error handling to use errors.Is and errors.As with proper wrapping.
High-intent search queries and answers about installing and using this skill.
Wrap errors with %w to preserve originals and transform them with %v to hide internals. Inspect wrapped errors reliably using errors.Is for sentinel values and errors.As for typed errors to ensure robust checks across API boundaries.
Defer error handling in Go requires reporting or properly propagating errors safely. Ensure errors are handled exactly once by avoiding silent ignores and managing defer-related errors without duplicate processing, maintaining code robustness.
Use panic in Go for truly exceptional, unrecoverable failures rather than routine control flow. Avoid misused panics by returning errors normally, ensuring your error handling remains robust and maintainable across package boundaries.
Refactor Go code by replacing direct error comparisons with errors.Is for sentinel checks and errors.As for type assertions. Apply proper wrapping to preserve error context across API boundaries and callers.
Go errors get silently ignored or double-handled due to inconsistent checks and improper wrapping. Enforce exactly-once handling by using errors.Is, errors.As, and proper wrapping to avoid silent ignores and double-processing.
Yes, this approach refactors Go libraries to provide stable, inspectable errors across API boundaries. It enforces guidance for wrapping versus transforming errors so callers receive consistent, robust error responses.
rubiojrIntegrate Go packages into Rugo scripts via the require keyword.
DIGI-UWAutomate browser-based QA testing for OpenELIS Global with Playwright and generate pass/fail reports.
Oruga420Provide idiomatic Go patterns for concurrency, error handling, and package design.
TheBushidoCollectiveImplement Go error handling with wrapping, unwrapping, and sentinel errors.
