error-recovery

Classify workflow failures and attempt up to three automatic recovery steps.

91|10|Updated Oct 4, 2025
One-click install
npx skills add https://github.com/marcusgoll/Spec-Flow --skill error-recovery-marcusgoll
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-recovery
Source: https://github.com/marcusgoll/Spec-Flow/tree/main/.claude/skills/error-recovery
Command: npx skills add https://github.com/marcusgoll/Spec-Flow --skill error-recovery-marcusgoll

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Classify workflow failures into actionable categories and execute recovery strategies. Use this skill when a sprint/feature fails during implementation to determine if auto-fix is possible or manual intervention required.

Core Features & Use Cases

  • Classify failures using a decision tree to determine if auto-recovery is possible or manual intervention is required.
  • Auto-fix strategies: attempt up to 3 automated recovery steps, escalating if still failing.
  • Critical failures halt automatically and escalate for user intervention.
  • Unknown failures default to a safe, conservative path to avoid silent errors.
  • Works across CI, testing, deployments and release pipelines.

Quick Start

  1. When a workflow component fails, classify the failure using the decision tree below
  2. If fixable: execute auto-fix strategies (max 3 attempts)
  3. If critical: stop immediately, report to user
  4. If unknown: treat as critical (safe default)

Frequently Asked Questions about error-recovery

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

FAQPage Schema
How do I classify and automatically recover CI pipeline failures?

Classify workflow failures using a decision tree to determine if auto-recovery is possible or manual intervention is required. The Skill applies up to 3 automated recovery attempts, stops on critical blockers, and escalates unresolved cases for user review.

What types of failures can be automatically fixed in DevOps workflows?

Auto-fix strategies handle failures in CI pipelines, security scans, deployments, tests, builds, dependencies, and infrastructure. Unknown failures default to a safe, conservative path to prevent silent errors and unnecessary escalation.

When should I use automated error recovery versus manual intervention?

Use automated recovery when failures are classifiable as fixable through the decision tree. Critical blockers halt immediately and escalate to you; unknown failures also trigger manual review to avoid masking deeper issues.

Can error recovery work across different pipeline stages like testing and deployment?

Yes, error recovery applies to sprint and feature workflows across CI, testing, deployments, and release pipelines. It classifies failures at each stage and executes recovery strategies appropriate to that context.

What happens if automated fixes fail on the first attempt?

The Skill retries up to 3 times with different auto-fix strategies before escalating. If all attempts fail or a critical failure is detected, the workflow stops and reports to you for manual intervention.