Add Error Handling Automatically

The problem

Leaking stack traces and database internals in production responses creates massive security risks. Inconsistent error formats across your API make it impossible for frontend developers to build reliable client-side handling.

What it does

• Detects your framework and architecture to implement native-feeling, centralized error handlers and middleware.
• Transforms raw exceptions into safe, machine-readable JSON responses with stable error codes and request IDs.
• Protects async workflows by ensuring rejected promises reach handlers instead of crashing the process.
• Categorizes failures into specific types like validation, conflict, and auth errors with appropriate HTTP status codes.
• Sanitizes logs to prevent sensitive data like tokens, passwords, and PII from leaking into your observability stack.

Frameworks & tools

Works with any Node.js, Python, or Go web framework. Adapts to existing loggers, test suites, and package managers found in your workspace.

Why this beats prompting it yourself

Manually wrapping every route in try-catch blocks is brittle and repetitive. This skill builds a scalable, centralized foundation that preserves internal diagnostic traces while strictly enforcing public data boundary rules.

Use cases

• Standardizing 4xx/5xx responses across a legacy Express or FastAPI service.
• Adding custom exception classes that map database constraints to client-safe conflict errors.
• Securing production logs by filtering out PII and credentials from error payloads.
• Implementing global async error protection to stop unhandled promise rejections.

Known limitations

Requires read access to the project workspace to detect architectural patterns. Cannot test live third-party service failures without mocks or existing integration tests.