crash-recovery

Retrieve recent pipeline states from YAML files for session recovery.

3|1|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/OmniNode-ai/omniclaude --skill crash-recovery-omninode-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crash-recovery
Source: https://github.com/OmniNode-ai/omniclaude/tree/main/plugins/onex/skills/crash-recovery
Command: npx skills add https://github.com/OmniNode-ai/omniclaude --skill crash-recovery-omninode-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you quickly understand the state of your work after an unexpected session end or crash by showing recent pipeline statuses.

Core Features & Use Cases

  • Session Recovery: View recent pipeline states to orient yourself after a crash.
  • Progress Tracking: See ticket ID, current phase, branch, and modification time for active work.
  • Use Case: After your Claude session unexpectedly closes, use this Skill to see which tickets were being worked on and in what stage, allowing you to resume efficiently.

Quick Start

Use the crash-recovery skill to show the 10 most recently modified pipelines.

Frequently Asked Questions about crash-recovery

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

FAQPage Schema
How do I recover pipeline state after a session crash or unexpected interruption?

To recover pipeline state after a session crash, you can scan previously saved YAML files to retrieve recent ticket IDs, titles, phases, and branches. This allows you to quickly orient yourself and resume your work from the exact point of interruption.

What information can I retrieve from pipeline state files for workflow recovery?

Retrieving pipeline state from YAML files provides the ticket ID, current workflow phase, active branch, and last modification time. This data is sorted by recency to help you identify exactly which tasks were in-progress when the crash occurred.

How do I filter in-progress pipelines to find what I was debugging before a crash?

Filtering in-progress pipelines scans the state files and displays only the active workflows currently being debugged. This isolates the specific ticket ID, phase, and branch you need to resume without sorting through completed or abandoned work.

Can I output recovered pipeline states in JSON format for automated workflow debugging?

Yes, recovered pipeline states can be output in JSON format. This allows automated workflow debugging scripts to parse the ticket ID, phase, and branch data directly, enabling programmatic session recovery and state management integration.

Do I need pyyaml installed to retrieve recent pipeline states from YAML files?

Yes, pyyaml is required as a dependency to parse and retrieve recent pipeline states from YAML files. The library handles reading the ticket ID, phase, and branch data stored in the state files to ensure accurate crash recovery.

How many recently modified pipelines does crash recovery show by default?

Crash recovery shows the 10 most recently modified pipelines by default. It scans the state files sorted by modification time to display the ticket ID, title, phase, and branch for quick session orientation after an interruption.