Verified:GitHub

error-handling-patterns

Standardize error handling, propagation, and graceful degradation in multi-service architectures.

2|Updated Nov 21, 2025

Search Tags:#logging #resilience #error-handling #circuit-breaker #exception-handling #graceful-degradation #retry-patterns

Ready to run

npx skills add https://github.com/maxjuniorbr/segflow-crm --skill error-handling-patterns-maxjuniorbr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: error-handling-patterns
Source: https://github.com/maxjuniorbr/segflow-crm/tree/main/.cursor/skills/error-handling-patterns
Command: npx skills add https://github.com/maxjuniorbr/segflow-crm --skill error-handling-patterns-maxjuniorbr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Este skill padroniza padrões de tratamento de erros para aumentar a resiliência de aplicações, incluindo como tratar exceções, propagar erros e aplicar degradação graciosa.

Core Features & Use Cases

Padronização de hierarquia de erros e tipos de falha.
Estratégias de recuperação como retry, circuit breaker e degradação graciosa.
Guia de mensagens de erro claras e consistentes para usuários e desenvolvedores.

Quick Start

Implemente um tratamento de erros com logs contextuais em uma nova funcionalidade.

Frequently Asked Questions about error-handling-patterns

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

FAQPage Schema

How do I implement a circuit breaker for multi-service architectures?▼

Implement a circuit breaker for multi-service architectures by standardizing failure detection, blocking calls to degraded downstream services, and applying graceful fallbacks to maintain application availability. This prevents cascading failures across dependent services.

What is graceful degradation in error handling?▼

Graceful degradation in error handling is a resilience strategy that allows applications to maintain partial functionality during failures by applying standardized error hierarchies, consistent error types, and fallback procedures instead of crashing entirely.

How do I standardize exception handling and error propagation across APIs?▼

Standardize exception handling and error propagation across APIs by defining clear error hierarchies, using consistent error types, and generating clear, contextual error messages for both users and developers consuming the interface.

What's the best way to add contextual logging to retry patterns?▼

Add contextual logging to retry patterns by incorporating standardized error hierarchies and consistent failure types into your logging strategy, ensuring each retry attempt captures the error context needed for diagnosing transient failures.

When should I apply retry patterns instead of circuit breakers?▼

Apply retry patterns for transient network failures and circuit breakers when a downstream service is persistently degraded. Standardizing both resilience strategies ensures robust error propagation and graceful degradation in multi-service architectures.

Does this error handling approach work for asynchronous error management?▼

Yes, this error handling approach works for asynchronous error management by standardizing error propagation, applying consistent error types, and integrating contextual logging within asynchronous workflows and multi-service architectures.