Results for “exception-handling”

Provides patterns for robust error handling across TypeScript, Python, and Go, including typed errors, error boundaries, retries, circuit breakers, and user-facing error messages.

跨 TypeScript、Python、Go 的健壮错误处理模式——涵盖类型化错误、错误边界、重试策略及优雅降级

Python code-quality anti-patterns and review checks: exception-hierarchy correctness, singleton identity comparison, narrow exception handling, wildcard-import avoidance, magic-number naming, and dead-local removal. Use when reviewing or self-reviewing Python code for correctness and readability defects that linters and reviewers should catch.

Handle errors as values using fp-ts Either and TaskEither, replacing try/catch with predictable, type-safe error handling patterns.

Audit a codebase for silent failures, swallowed exceptions, and observability gaps across Sentry and Langfuse, then produce a phased fix plan. Use when the user says "errors aren't showing in Sentry", "things fail silently", "empty catch blocks", "add error handling", "check my Langfuse tracing", or is hardening.

Provides patterns for robust error handling across TypeScript, Python, and Go, covering typed errors, error boundaries, retries, circuit breakers, and user-facing messages.

Patterns for robust error handling across TypeScript, Python, and Go. Covers typed errors, error boundaries, retries, circuit breakers, and user-facing error messages.

Error Handling Patterns

Design, review, and troubleshoot Salesforce Flow fault handling with error logging and bulk-safe automation paths.

Error Handling — Agent Arena

Stop throwing everywhere - handle errors as values using Either and TaskEither for cleaner, more predictable code

Use when the team needs a strategy for validation errors, API failures, job retries, user-facing error UX, observability, or recovery behavior. Trigger on requests to design error handling across frontend, backend, and integrations.

Stop throwing everywhere - handle errors as values using Either and TaskEither for cleaner, more predictable code

Build a vulnerability exception and risk acceptance tracking system with approval workflows, compensating controls documentation, and expiration management.

Use when detecting, responding to, or recovering from system failures, outages, security breaches, or critical errors. This skill provides a structured incident response process for any type of failure, ensuring consistent handling, communication, and post-incident learning.

Runbook skill for failures: cron error, PA failure, cascade, gateway disconnect, semantic DB stale. Walks: detect → classify → diagnose → notify → log. Replaces ad-hoc failure handling. Triggers: "cron failed", "X is broken", "cascade", "incident", "gateway down", "PA failure".

Handle errors as values using fp-ts Either and TaskEither to write cleaner, more predictable TypeScript code.

HASH error handling patterns using error-stack crate. Use when working with Result types, Report types, defining custom errors, propagating errors with change_context, adding context with attach, implementing Error trait, or documenting error conditions in Rust code.

Urgent issue classification, root cause analysis, and fast-path routing for production hotfixes

Error handling review — silent failure detection, catch block analysis, error logging.

Incident response mode — diagnose a production issue, write a postmortem, add follow-up tasks to TODO.md. Use when user says "/incident [description]".

Package a customer escalation for engineering, product, or leadership as a decision-ready handoff — impact, timeline, facts vs. hypotheses, and a specific ask with an owner.

Use with analysis-agent or task-agent for task-local transaction, isolation, and conflict decisions. Do not use without a transaction decision or as task owner.

Handle errors as values using fp-ts Either and TaskEither for cleaner, more predictable TypeScript code. Use when implementing error handling patterns with fp-ts.

Design error prevention, detection, and recovery experiences that minimize user frustration.

Stop throwing everywhere - handle errors as values using Either and TaskEither for cleaner, more predictable code

Implements inbound email processing in Apex: parsing messages, creating or updating records, handling attachments, and configuring Email Service routing.

Stop throwing everywhere - handle errors as values using Either and TaskEither for cleaner, more predictable code

Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready.

Follow best practices for asynchronous programming in C#, including naming, return types, exception handling, performance, and common pitfalls.