agent-recovery

Recovers interrupted AI agent ticket work from durable GitHub state and checkpoints.

1|Updated Sep 11, 2026
One-click install
npx skills add https://github.com/rebuildup/my-web-2026 --skill agent-recovery-rebuildup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-recovery
Source: https://github.com/rebuildup/my-web-2026/tree/main/skills/agent-recovery
Command: npx skills add https://github.com/rebuildup/my-web-2026 --skill agent-recovery-rebuildup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agent sessions, sandboxes, and processes can crash or lose context mid-task, and relying on conversation history alone makes recovery impossible. This Skill defines a canonical recovery path that rebuilds ticket work from durable project state instead of fragile session memory. ## Core Features & Use Cases - Durable state recovery: Reconstructs work from GitHub Issues, Projects, branches, Draft PRs, stack predecessors, and structured recovery checkpoints rather than native session state. - Split-brain prevention: Uses execution generations, leases, and fencing tokens with compare-and-set ownership so stale agents cannot perform duplicate integrations or external writes. - Validation and side-effect reconciliation: Re-evaluates validation results against the current code snapshot and reconciles external side effects (deploys, migrations, publishes) against remote actual state before retrying. - Use Case: A sandbox running a multi-hour implementation crashes mid-validation. A fresh agent reads the Issue, PR, and latest checkpoint, acquires a new fencing token, reconciles child subagents, and resumes from the last verified state without duplicating side effects. ## Quick Start Ask the agent to recover the interrupted ticket work for a given GitHub Issue by reading the project state, branches, PRs, and latest recovery checkpoint, then resuming from the validated snapshot.

Frequently Asked Questions about agent-recovery

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

FAQPage Schema
How do I recover an AI agent session after a crash?

Recover from durable state rather than the lost conversation: identify the GitHub Issue, Project, target release, ticket branch, and Draft PR, then read the latest recovery checkpoint. A fresh agent re-acquires ownership with a new execution generation and resumes from the validated snapshot.

What is a recovery checkpoint for AI agents?

A recovery checkpoint is a structured record of externalizable facts needed to resume work: issue ID, branch, PR number, base SHA, completed steps, next steps, pending validation, and blockers. It deliberately excludes private chain-of-thought and machine-specific paths.

How do you prevent duplicate execution when two agents run the same task?

Use a Supervisor-held lease with execution generations and fencing tokens acquired via compare-and-set. Stale generations are rejected from branch integration and external writes, and the fencing token is revalidated immediately before each external side effect.

Can validation results be reused after an interrupted run?

Only when the validated snapshot exactly matches the current code snapshot and the check's determinism conditions still hold. If a rebase or checkpoint change altered the code, previous green results must be re-run against the new SHA.

What happens to child subagents when the parent agent crashes?

Child lifecycles are owned by the Supervisor, not the parent process, so children are not immediately cancelled. A recovered coordinator rediscovers children, classifies them as running, completed, failed, or orphaned, collects immutable results, and retries or respawns as needed.

When should I not rely on native session resume?

Native session or thread resume is only a fast-path optimization, never the source of truth. After any resume, verify consistency against the Issue, Project, branch, PR, stack, and checkpoint state before continuing work.