error-handling

Standardize error handling across TypeScript, Python, and Go codebases.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/nazrulsoftwaredev/NIT_CRM_2 --skill error-handling-nazrulsoftwaredev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-handling
Source: https://github.com/nazrulsoftwaredev/NIT_CRM_2/tree/main/.agents/skills/error-handling
Command: npx skills add https://github.com/nazrulsoftwaredev/NIT_CRM_2 --skill error-handling-nazrulsoftwaredev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the challenge of inconsistent error handling, silent failures, and poor user feedback in complex applications by providing standardized patterns for error propagation and recovery.

Core Features & Use Cases

  • Typed Error Hierarchies: Define structured, domain-specific error classes for TypeScript, Python, and Go to ensure type safety and consistent API responses.
  • Resilience Patterns: Implement retry logic with exponential backoff and circuit breakers to handle transient failures in external dependencies.
  • User-Facing Feedback: Map technical errors to human-readable messages while maintaining secure, detailed server-side logging.
  • Use Case: Use these patterns to refactor a service that currently swallows database exceptions, ensuring that every error is logged with context and the client receives a meaningful, standardized error response.

Quick Start

Apply the error handling patterns by defining a base AppError class and wrapping your service layer calls in a result-based pattern to ensure all failures are explicitly handled.

Frequently Asked Questions about error-handling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize error handling across TypeScript, Python, and Go codebases?

Standardize error handling by defining structured, domain-specific typed error hierarchies and wrapping service layer calls in a result-based pattern to ensure all failures are explicitly handled.

What's the best way to implement retry logic with exponential backoff for external dependencies?

Implement resilient retry logic with exponential backoff and circuit breakers to handle transient failures in external dependencies, ensuring robust failure recovery for production services.

How do I map internal technical errors to user-facing messages without exposing sensitive details?

Map technical errors to human-readable messages for the client while maintaining secure, detailed server-side structured logging to ensure robust observability and safe user feedback.

How do I fix silent failures when my service swallows database exceptions?

Fix silent failures by refactoring services with explicit error propagation patterns, ensuring every database exception is logged with context and returns a meaningful, standardized error response.

Does this error handling approach work for building production-grade APIs?

Yes, this error handling approach enforces explicit error management, structured logging practices, and consistent API responses, making it suitable for building robust, production-grade APIs.