go-error-handling-patterns

What problem does it solve?

Go applications often duplicate error handling logic, leading to inconsistent messages and debugging challenges. This skill provides a unified AppError type and a standardized error workflow across services, including stack traces for debugging while emitting user-safe messages to clients.

Core Features & Use Cases

• Unified AppError type with Code, Message, Detail, HTTPStatus, and stack traces, enabling consistent error responses and easier tracing.
• Constructors for common domain errors (NotFound, Validation, Unauthorized, Forbidden, Internal, TenantMismatch), plus a simple Internal wrapper for unexpected causes.
• Error wrapping with fmt.Errorf %w to preserve error chains for errors.Is / errors.As.
• Domain-level error catalogs and sentinel errors to centralize domain semantics and reduce duplication.
• PII-safe user messages with internal details kept in non-serialized fields for debugging.

Quick Start

Start using the shared AppError constructors in your services to emit consistent, safe errors.