skills.rest
srulyt
srulytCOMMUNITY
Explore all skills by this author →
GitHub

error-recovery

Diagnose and recover from build, test, and file operation errors.

2|2|Updated Jan 20, 2026
Search Tags:#debugging#troubleshooting#error handling#escalation#test failure#build recovery
One-click install
npx skills add https://github.com/srulyt/srulys-agent-packs --skill error-recovery-srulyt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: error-recovery
Source: https://github.com/srulyt/srulys-agent-packs/tree/main/agent-packs/agentic-developer/.roo/skills/error-recovery
Command: npx skills add https://github.com/srulyt/srulys-agent-packs --skill error-recovery-srulyt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured approach to handling errors during task execution, ensuring that issues are systematically diagnosed, resolved, or escalated appropriately.

Core Features & Use Cases

  • Error Classification: Differentiates between self-recoverable errors and those requiring external intervention.
  • Automated Recovery Strategies: Implements specific patterns for build failures, test failures, and file operation errors.
  • Use Case: When a build process fails due to a syntax error, this Skill will analyze the error message, attempt to locate and fix the issue, and retry the build up to a defined limit before escalating.

Quick Start

Use the error-recovery skill to handle a build failure by analyzing the error message and attempting a fix.

Frequently Asked Questions about error-recovery

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

FAQPage Schema
How do I systematically recover from build failures during task execution?▼

Systematic error resolution classifies failures by analyzing error messages, applying targeted fixes, and retrying the operation up to a defined limit before escalating. This structured approach prevents automated workflows from halting unexpectedly during task execution.

What is the best way to handle test failures in an automated workflow?▼

Handling test failures involves classifying the failure as self-recoverable or requiring external intervention, applying automated recovery strategies, and escalating with standardized reporting formats if retries exceed the defined threshold.

When should I escalate errors to an orchestrator instead of retrying automatically?▼

You should escalate errors to an orchestrator when targeted retry attempts exceed a predefined limit or when the issue classification indicates the error requires external intervention rather than automated recovery strategies.

Does this error handling approach work for file operation errors and build recovery?▼

Yes, this error handling approach works for file operation errors and build recovery by implementing specific patterns to classify issues, diagnose root causes, and apply targeted fixes across different failure types encountered during task execution.

How do I troubleshoot task execution errors when automated retry attempts fail?▼

When automated retry attempts fail, troubleshooting requires triggering escalation protocols to report the failure to an orchestrator using defined formats, ensuring the issue receives external intervention rather than continuing unsuccessful recovery loops.

Related Skills

Explore More Software Engineering Skills→
BurburtonBurburton
2

CI Failure Analysis

Analyze CI pipeline logs to diagnose build, test, and infrastructure failures.

Community
Advanced
masharrattmasharratt
14

cfn-intervention-system

Detect human intervention requirements in CFN Loop automation workflows.

Community
Advanced
tigredonortetigredonorte

follow-up-pr

Monitor PR CI status and apply automated fixes until checks pass.

Community
Advanced
terrylicaterrylica

mt5-log-reader

Parse MetaTrader 5 log files to validate execution and surface errors.

Community
Intermediate