error-handling-patterns

Automate error-handling patterns with retries and circuit breakers across languages.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/m-salauddin/Learning-Management-System- --skill error-handling-patterns-m-salauddin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-handling-patterns
Source: https://github.com/m-salauddin/Learning-Management-System-/tree/main/.agent/skills/error-handling-patterns
Command: npx skills add https://github.com/m-salauddin/Learning-Management-System- --skill error-handling-patterns-m-salauddin

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides reusable error-handling patterns across programming languages to improve reliability, observability, and user experience by standardizing how exceptions, result types, retries, and graceful degradation are implemented.

Core Features & Use Cases

  • Cross-language patterns: Exceptions vs Result types, NotFound handling, retries, and circuit breakers applied consistently.
  • Design guidance: Recommended logging, tracing, and fail-fast strategies to reduce debugging time and cascading failures.
  • Use Case: Teams introducing robust error handling in APIs, data pipelines, and distributed systems can adopt these patterns to improve resilience and maintainability.

Quick Start

To begin, review the provided examples and implement a basic try/except flow in your language of choice, then extend with a circuit breaker and retry strategy as shown in the examples.

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 robust error handling for distributed systems?

Implement robust error handling by standardizing exceptions, Result types, retries, and circuit breakers. This approach prescribes language-specific implementations to improve resilience and maintainability across APIs and data pipelines.

What is the difference between using exceptions and Result types for error propagation?

Exceptions interrupt control flow for unexpected failures, while Result types explicitly encode success or error in the return value. This Skill applies both cross-language patterns consistently to standardize propagation and improve observability across your codebase.

When do I need a circuit breaker and retry strategy in my API?

You need a circuit breaker and retry strategy when preventing cascading failures in distributed systems. This Skill provides design guidance for implementing fail-fast strategies and standardized logging to reduce debugging time during API outages.

How do I start adding fail-fast strategies and standardized tracing to my data processing pipelines?

Start adding fail-fast strategies by reviewing the provided examples and implementing a basic try/except flow in your language of choice. Then extend the implementation with a circuit breaker and retry strategy as demonstrated in the references.

Can I use these error-handling patterns across different programming languages?

Yes, you can use these error-handling patterns across different programming languages. The Skill provides reusable, cross-language patterns for exceptions, Result types, and graceful degradation, prescribing language-specific implementations for consistent integration.