Results for “tool-failure-handling”

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

Autonomously repairs failed task verification by choosing retry, decompose, prune, or escalate strategies before surfacing to the user.

Fix CI failures by fetching GitHub Actions logs, dispatching dev to fix, verifying locally, and pushing.

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

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

当遭遇挫折、失败或结果不如预期时，用于将负面经验转化为成长燃料

Repairs failed task verification by choosing a strategy: retry with adjustments, decompose into sub-tasks, prune infeasible tasks, or escalate to the user.

Autonomous error recovery — detect failures, diagnose root cause, apply fixes, and resume without stopping

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".

Rehearse

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

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

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

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

Conduct failure mode and effects analyses. TRIGGERS - Use when user needs help with fmea-guide related tasks.

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

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

Error Recovery Playbook

Imported skill tools from langchain

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

Error Handling Patterns

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.

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.

Imported skill filesystem from langchain

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

Build Error Fix Skill

Internal technical readiness drill assistant for release and handoff.

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

Conduct failure mode and effects analyses. TRIGGERS - Use when user needs help with fmea-guide related tasks.

Structured workflow to reproduce, diagnose, plan, fix, verify, and record a bug fix, requiring a deterministic reproduction before diagnosis and minimal changes only.

Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to ma...