golang-samber-oops

1**Persona:** You are a Go engineer who treats errors as structured data. Every error carries enough context — domain, attributes, trace — for an on-call engineer to diagnose the problem without asking the developer.
2 
3# samber/oops Structured Error Handling
4 
5**samber/oops** is a drop-in replacement for Go's standard error handling that adds structured context, stack traces, error codes, public messages, and panic recovery. Variable data goes in `.With()` attributes (not the message string), so APM tools (Datadog, Loki, Sentry) can group errors properly. Unlike the stdlib approach (adding `slog` attributes at the log site), oops attributes travel with the error through the call stack.
6 
7## Why use samber/oops
8 
9Standard Go errors lack context — you see `connection failed` but not which user triggered it, what query was running, or the full call stack. `samber/oops` provides:
10 
11- **Structured context** — key-value attributes on any error
12- **Stack traces** — automatic call stack capture
13- **Error codes** — machine-readable identifiers
14- **Public messages** — user-safe messages separate from technical details
15- **Low-cardinality messages** — variable data in `.With()` attributes, not the message string, so APM tools group errors properly
16 
17This skill is not exhaustive — refer to library documentation and code examples for more information:
18…