error-recovery

Diagnose verification gate failures and apply minimal rollback fixes.

2|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/yutna/vibe-next-template --skill error-recovery-yutna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-recovery
Source: https://github.com/yutna/vibe-next-template/tree/main/.claude/skills/error-recovery
Command: npx skills add https://github.com/yutna/vibe-next-template --skill error-recovery-yutna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams recover from gate, review, or verification failures by automatically diagnosing the root cause, selecting a rollback, and applying the smallest valid fix.

Core Features & Use Cases

  • Failure classification across error scenarios (unclear requirements, planning errors, implementation bugs, lint/type issues, test regressions, verification mismatches)
  • Rollback-phase selection and safe re-execution of downstream steps
  • Retry policy with a defined budget and clear escalation when exhausted
  • Do not use for unrelated areas or speculative fixes

Quick Start

Describe the failure and trigger the recovery loop to classify the issue and apply the smallest valid rollback.

Frequently Asked Questions about error-recovery

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

FAQPage Schema
How do I automate failure recovery and rollback for failing verification gates?

Automated failure recovery for verification gates works by diagnosing the root cause of failures, selecting a rollback phase, and applying minimal fixes to resume the pipeline.

What is the best way to diagnose test suite regressions and lint check failures?

Diagnosing test suite regressions and lint check failures involves classifying the error scenario, selecting a safe rollback phase, and re-executing downstream steps with iterative retries.

How do I fix configuration drift and implementation bugs during code reviews?

Fixing configuration drift and implementation bugs during code reviews requires classifying the failure type, applying the smallest valid rollback, and verifying the recovery with a retry policy.

Does automated error recovery work for quality gates and code review checks?

Automated error recovery works for quality gates and code review checks by classifying failures, selecting rollback phases, and applying minimal fixes to satisfy verification requirements.

What are the limitations of using automated rollback for verification mismatches?

Automated rollback for verification mismatches is limited by a defined retry budget and should not be used for unrelated areas or speculative fixes when the retry policy is exhausted.