forge-error-handling

What problem does it solve?

It prevents production code from swallowing errors, leaking internal details to clients, and creating inconsistent failure modes that are hard to debug or recover from.

Core Features & Use Cases

• Catch only at process boundaries to avoid scattering error handling through business logic while still ensuring callers see consistent outcomes.
• Use Result types for expected failures and throw for unexpected ones, enabling exhaustive, type-safe routing on error codes.
• Sanitize client responses with request_id correlation while logging full structured error details server-side.
• Make retries safe by requiring idempotency for retried operations, enforcing attempt bounds, and using exponential backoff with jitter.
• Crash loud on invariant violations and exit on unhandled errors to avoid silent partial failures and corrupted state.

Quick Start

Use the forge-error-handling skill when writing or reviewing an HTTP handler, job entry point, or message consumer so that each failure path is correctly categorized, logged, and returned as a safe, consistent client response.