error-recovery

Diagnose validation failures and apply a three-strike recovery protocol.

2|Updated Apr 8, 2026

Search Tags:#debugging #validation #evidence #error-recovery #escalation #root-cause #recovery-protocol

Ready to run

npx skills add https://github.com/krzemienski/validationforge --skill error-recovery-krzemienski

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: error-recovery
Source: https://github.com/krzemienski/validationforge/tree/main/skill-audit-workspace/error-recovery/skill-snapshot
Command: npx skills add https://github.com/krzemienski/validationforge --skill error-recovery-krzemienski

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Diagnoses and recovers from validation failures using a disciplined, three-strike protocol that aims to fix root causes rather than masking symptoms.

Core Features & Use Cases

Structured diagnosis and targeted fixes: Identify root causes from full error output and apply minimal changes.
Three-strike escalation: If the first fix fails, attempt alternative tools/paths, then rethink the approach and escalate.
Evidence-backed validation: Re-validate after each strike and log all attempts using the provided templates.

Quick Start

Start by inspecting the full error output for the failing step and apply the Strike 1 targeted fix, then re-run the same validation.

Frequently Asked Questions about error-recovery

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

FAQPage Schema

What is a structured debugging protocol for recovering from build failures and runtime crashes?▼

A structured debugging protocol for validation failures uses a 3-strike approach: apply a targeted minimal fix, re-validate the same step, and escalate after three failed attempts. It addresses root causes rather than masking symptoms across build and runtime errors.

How do I diagnose and fix validation failures without masking the root cause?▼

To diagnose validation failures, inspect the full error output and apply the smallest possible targeted fix. Re-run the exact same validation step to confirm the root cause is resolved before proceeding to alternative approaches.

When should I escalate a debugging effort after repeated runtime or database errors?▼

You should escalate debugging efforts after three failed strikes: an initial targeted fix, an alternative tool or path attempt, and a broader approach rethink. Escalation ensures persistent validation failures get broader review rather than endless localized retries.

Does the 3-strike error recovery method work for network and authentication errors?▼

Yes, the 3-strike error recovery method works for network, authentication, and database errors. It applies across validation journeys by requiring full error output recording, minimal fixes, and re-validation after each strike before escalating.

What is the best way to log error recovery attempts during validation journeys?▼

The best way to log error recovery attempts is using structured error-log templates. Recording full error output and each strike's applied fix creates an evidence-backed trail that validates whether the root cause was actually addressed.

Why does my validation keep failing after applying a targeted fix to a runtime crash?▼

Validation keeps failing after a targeted fix when the root cause requires a broader rethink. If the first strike fails, attempt alternative tools or paths on the second strike, then fundamentally rethink the approach and escalate on the third strike.