feature-recovery

Diagnose failed implementations from error outputs and generate recovery plans.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/pcortes/swarm-attack --skill feature-recovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-recovery
Source: https://github.com/pcortes/swarm-attack/tree/main/default-skills/recovery
Command: npx skills add https://github.com/pcortes/swarm-attack --skill feature-recovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the diagnosis of implementation failures, providing clear recovery steps or escalation reasons. It saves developers significant time by quickly identifying root causes and suggesting solutions, reducing manual debugging and accelerating development cycles.

Core Features & Use Cases

  • Automated Failure Diagnosis: Pinpoints the root cause of various errors, including test failures, timeouts, runtime errors, Git conflicts, and authentication issues.
  • Recoverability Assessment: Determines if an issue can be automatically fixed by an AI agent or if it requires human intervention.
  • Actionable Recovery Plans: Generates specific, step-by-step instructions for automatic recovery or clear guidance for human resolution.
  • Use Case: A feature implementation fails due to a missing import. This Skill automatically analyzes the error output, identifies the missing import, and suggests adding the correct import statement, allowing the AI to retry and successfully complete the task.

Quick Start

Analyze the provided error output from a failed test run and generate a recovery plan, including root cause, recoverability, and suggested actions.

Frequently Asked Questions about feature-recovery

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

FAQPage Schema
How do I diagnose the root cause of a failed test or runtime error?

Root cause diagnosis extracts the underlying issue from error outputs by parsing failure messages, classifying error types, and identifying what went wrong. This Skill analyzes test failures, timeouts, runtime errors, Git conflicts, authentication issues, and network failures to pinpoint the specific problem so you understand exactly what broke.

Can I automatically recover from implementation failures without manual debugging?

Automatic recovery depends on recoverability assessment. This Skill determines whether an error can be fixed automatically—such as adding a missing import or correcting a syntax error—or if it requires human intervention, then generates concrete recovery steps or escalation guidance accordingly.

What types of errors can be analyzed and recovered automatically?

Recoverable errors include missing imports, syntax mistakes, configuration issues, and common runtime problems that can be systematically fixed. Non-recoverable errors—such as infrastructure unavailability or design flaws—are flagged with escalation reasons so you know when to involve human review instead of attempting automation.

How does this speed up development cycles when implementations fail?

By automating failure diagnosis and generating actionable recovery plans, this Skill eliminates manual debugging overhead. Developers get immediate root cause identification and step-by-step recovery instructions, allowing faster retries and reducing time spent analyzing logs and error messages.

What information does the recovery plan output include?

The recovery plan outputs root cause, recoverability status, concrete recovery steps, human-readable instructions, suggested actions for automation, and escalation reasons. This structured JSON payload gives both AI agents and developers everything needed to resolve or escalate the failure.