What is the recommended way to wrap errors in Go?

The recommended approach is using fmt.Errorf with the %w verb, like: fmt.Errorf("context: %w", err). This allows you to add context while preserving the original error for future checks.

How do I handle multiple errors in a goroutine?

The most idiomatic way is to use a channel to collect errors or use the 'golang.org/x/sync/errgroup' package, which coordinates multiple goroutines and returns the first non-nil error encountered.

Is it better to use panic or return an error in Go?

Always prefer returning errors for expected failure conditions. Panics should be reserved strictly for truly exceptional, unrecoverable situations like out-of-bounds array access or failed mandatory initialization.

When should I use errors.Is vs errors.As?

Use errors.Is to check if an error matches a specific sentinel value (like ErrNotFound). Use errors.As to check if an error is of a specific type and to extract its data into a variable.

Go Modern Error Handling

Name: Go Modern Error Handling
Author: IvanTorresEdge

byIvanTorresEdge

API Development

Implements idiomatic Go error handling patterns following modern standards and best practices.

About

This skill equips Claude with specialized knowledge of Go 1.13+ error handling conventions, facilitating the creation of robust and maintainable Go applications. It covers essential patterns including sentinel error creation, context-aware error wrapping with the %w verb, and type-safe error checking using the errors.Is and errors.As functions. By utilizing these standardized patterns, developers can ensure clear error propagation, easier debugging, and consistent behavior across complex Go codebases and concurrent operations.

Key Features

Implementation of custom error types with Unwrap support
0 GitHub stars
Type-safe error checking with errors.Is and errors.As
Clean early-return patterns to reduce nesting
Modern error wrapping and context propagation using %w
Concurrent error management using errgroup and channels

Use Cases

Refactoring legacy Go code to use modern error wrapping conventions
Implementing safe error propagation in high-concurrency microservices
Designing custom validation error types for API response mapping

About

Key Features

Implementation of custom error types with Unwrap support
0 GitHub stars
Type-safe error checking with errors.Is and errors.As
Clean early-return patterns to reduce nesting
Modern error wrapping and context propagation using %w
Concurrent error management using errgroup and channels

Use Cases

Refactoring legacy Go code to use modern error wrapping conventions
Implementing safe error propagation in high-concurrency microservices
Designing custom validation error types for API response mapping