error-handling-patterns

Provide structured error-handling patterns for exceptions, result types, and graceful degradation.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/junaid-ali-ruk/auto-linkedin --skill error-handling-patterns-junaid-ali-ruk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-handling-patterns
Source: https://github.com/junaid-ali-ruk/auto-linkedin/tree/main/.gemini/skills/error-handling-patterns
Command: npx skills add https://github.com/junaid-ali-ruk/auto-linkedin --skill error-handling-patterns-junaid-ali-ruk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides structured guidance for building robust error-handling strategies across multiple programming languages, reducing debugging time and improving system reliability.

Core Features & Use Cases

  • Cross-language patterns such as exceptions vs Result types, error propagation, and retry and circuit-breaker strategies.
  • Language-specific examples (Python, TypeScript, Rust, Go) paired with universal templates to illustrate practical usage.
  • Use cases include designing resilient APIs, debugging production issues, and improving user-facing error messaging.

Quick Start

Use this skill to implement a robust error-handling strategy across a new feature by selecting a pattern (e.g., explicit Result type), adding a retry policy, and guarding external calls with a circuit breaker.

Frequently Asked Questions about error-handling-patterns

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

FAQPage Schema
What is the best way to handle errors across different programming languages?

A circuit breaker prevents system failure by stopping requests to a failing service. It provides graceful degradation during production issues, ensuring reliability when external API calls repeatedly timeout or error.

How do I implement a retry policy for external API calls?

To implement a retry policy, select a structured error-handling pattern like explicit Result types, then add retry logic to guard external calls. This improves system reliability by automatically recovering from transient failures.

Should I use exceptions or result types for resilient API design?

Choosing between exceptions and result types depends on your language paradigm. Structured patterns for both approaches provide explicit error propagation, improving user-facing error messaging and API reliability across different technical stacks.

How do I debug production issues with graceful degradation strategies?

Debug production issues by applying graceful degradation strategies alongside circuit breakers. These structured patterns isolate failing components, improve system observability, and maintain core functionality during partial outages.

Does this provide language-specific error handling examples for Python and Go?

Yes, it provides language-specific error handling examples for Python, TypeScript, Rust, and Go. These examples are paired with universal templates to illustrate practical usage for feature development and debugging.