crash-recovery

Diagnose PostgreSQL shared state and refresh projections to resume aidn repository work.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/leuzeus/aidn --skill crash-recovery-leuzeus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crash-recovery
Source: https://github.com/leuzeus/aidn/tree/main/scaffold/codex/crash-recovery
Command: npx skills add https://github.com/leuzeus/aidn --skill crash-recovery-leuzeus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Recover the repository to the smallest safe resumable state after an abrupt stop. This Skill helps realign local and shared runtime state, diagnose inconsistencies, and prepare a clean path to resume work without data loss.

Core Features & Use Cases

  • Diagnose shared state and local backlog mismatches
  • Reanchor planning, rematerialize projections, and regenerate handoff packets
  • Refresh runtime state and handoff readiness to resume work safely
  • Suitable for PostgreSQL-backed shared state or local-workflow interruptions

Quick Start

Immediately begin a crash-recovery session by following the prescribed runbook to reanchor and restore coordination after a crash.

Frequently Asked Questions about crash-recovery

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

FAQPage Schema
How do I recover a repository after an abrupt stop or crash?

Recover a repository after an abrupt stop by aligning local state with shared coordination, diagnosing mismatches, and determining the next safe command to resume work without data loss.

What causes local backlog artifacts to become stale or missing during runtime?

Local backlog artifacts become stale or missing when PostgreSQL shared state advances ahead of local files, requiring a crash-recovery process to diagnose mismatches and refresh projections.

How do I reanchor planning and rematerialize projections after an interrupted workflow?

Reanchor planning and rematerialize projections by following a prescribed runbook that regenerates handoff packets and refreshes runtime state to restore safe coordination after a crash.

When do I need to regenerate handoff packets for shared state synchronization?

Regenerate handoff packets when local files and PostgreSQL-backed shared state fall out of sync, ensuring backlog artifacts are refreshed and the repository reaches a safe resumable state.

Does crash-recovery work with PostgreSQL-backed shared state and local workflow interruptions?

Crash-recovery applies to both PostgreSQL-backed shared state and local-workflow interruptions, diagnosing shared state mismatches and refreshing runtime state to safely resume work.

Why does shared coordination state get ahead of local files after a runtime crash?

Shared coordination state gets ahead of local files when an abrupt stop prevents local backlog artifacts from updating, requiring state diagnosis and projection refresh to reestablish alignment.