Convert internal exceptions into structured API error responses with typed error taxonomy.
npx skills add https://github.com/hendrax5/ironman --skill error-handling-hendrax5
Please help me install this Agent Skill. Skill: error-handling Source: https://github.com/hendrax5/ironman/tree/main/skills/error-handling Command: npx skills add https://github.com/hendrax5/ironman --skill error-handling-hendrax5
This Skill enforces a consistent, safe approach to mapping internal exceptions into structured API error responses, preventing leaked stack traces and inconsistent status codes.
Implement the AppError hierarchy, throw typed errors in services and repositories, and register the centralized error-handler middleware so all routes forward exceptions and clients receive consistent JSON error responses.
High-intent search queries and answers about installing and using this skill.
To convert internal exceptions into structured API error responses, implement a typed AppError hierarchy and register centralized error-handler middleware that maps operational errors to canonical HTTP status codes and returns consistent JSON.
Preventing stack traces from leaking in API error responses requires centralized error-handler middleware that distinguishes operational from programming errors, suppressing stack traces in client-facing JSON output while logging full details with traceId internally.
The best way to map domain and infrastructure exceptions to HTTP status codes is using a hierarchical AppError taxonomy with Domain, Infra, and Auth subclasses, mapping validation failures to 422, not-found to 404, and database faults to 503.
Yes, centralized error-handler middleware works for microservices and API gateways by applying layered patterns across controllers, services, and repositories to ensure consistent error formatting and traceability across distributed backend services.
Throw typed errors in service and repository layers when wrapping infrastructure failures or encountering operational errors, allowing the centralized middleware to distinguish them from programming errors and apply the correct HTTP status mapping.
API endpoints return inconsistent HTTP status codes for similar errors when lacking a centralized error-handler middleware with a typed AppError taxonomy that enforces canonical HTTP status mapping and suppresses internal stack traces in client responses.
kennypallchizaca-coderCentralize backend exception mapping into consistent HTTP error responses.
cenjieImplements error handling for REST and GraphQL endpoints with retries and circuit breaking.
henriqueatilaGenerates REST APIs with routing, validation, and error handling in Go/Gin.
gizixImplement async error handling for Quart applications with JSON responses.
