go-errors
Go error handling patterns. Routes to specific patterns.
When & Why to Use This Skill
This Claude skill provides expert-level Go error handling patterns and best practices. It guides developers through essential Golang techniques such as error wrapping with context, defining sentinel errors, and performing type-safe error inspections using errors.Is and errors.As. By following these idiomatic patterns, developers can create more maintainable, debuggable, and robust Go applications while ensuring error context is preserved throughout the call stack.
Use Cases
- Implementing robust error wrapping using fmt.Errorf and the %w verb to maintain error context across different service layers.
- Defining and utilizing package-level sentinel errors to allow callers to perform specific error checks without tight coupling.
- Refactoring legacy Go codebases to utilize modern, type-safe error checking and custom error data extraction introduced in Go 1.13+.
- Standardizing error handling logic across a development team to ensure consistent debugging and observability patterns.
| name | go-errors |
|---|---|
| description | Go error handling patterns. Routes to specific patterns. |
Go Error Handling
Route by Need
- Wrapping errors with context → see wrapping/
- Defining sentinel errors → see sentinel/
- Checking error types → see checking/
Quick Check
- Never ignore errors (_ = fn())
- Wrap with context at boundaries
- Use errors.Is/As, not ==
Common Pattern
func ProcessFile(path string) error {
f, err := os.Open(path)
if err != nil {
return fmt.Errorf("open %s: %w", path, err)
}
defer f.Close()
if err := parse(f); err != nil {
return fmt.Errorf("parse %s: %w", path, err)
}
return nil
}