interruption-recovery

Capture and restore development task context across interruptions and sessions.

2|Updated May 10, 2026
One-click install
npx skills add https://github.com/freedomw1987/tree_monstor --skill interruption-recovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interruption-recovery
Source: https://github.com/freedomw1987/tree_monstor/tree/main/skills/interruption-recovery
Command: npx skills add https://github.com/freedomw1987/tree_monstor --skill interruption-recovery

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Long-running development tasks are constantly interrupted by breaks, system restarts, or context window limits, causing developers to lose hours re-explaining context when they return. This Skill eliminates that productivity loss by automatically saving task state and enabling instant context restoration.

Core Features & Use Cases

  • 4-Layer Recovery Architecture: Trigger detection, state snapshot, resume command generation, and agent restart with full context.
  • Auto-Save on Interruption: Captures dev-task state, session info, git status, and external memory sync before any break.
  • One-Command Resume: Three flexible resume modes (exact session, project name, or fresh session with injected state) fit any interruption duration.
  • Context Reconstruction: Recovers from generic template state files using git logs, session search, and interruption logs when auto-detection fails.

Quick Start

Use the interruption-recovery skill to save your current development task state before taking a break and resume it later with full context restored.

Frequently Asked Questions about interruption-recovery

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

FAQPage Schema
How do I restore development task context after a session interruption?

You can restore development task context after a session interruption by using automated snapshot creation and multi-mode resume commands to instantly reconstruct your previous state.

What is the best way to auto-save long-running dev tasks before a break?

The best way to auto-save long-running dev tasks is to use automated state capture, which records session info, git status, and external memory before any break occurs.

How does context reconstruction work when auto-detection fails?

Context reconstruction works by recovering from generic template state files using git logs, session search, and interruption logs to rebuild the missing development context.

Can I resume an interrupted task using just the project name?

Yes, you can resume an interrupted task using just the project name, as the system supports three flexible resume modes including exact session, project name, or fresh session with injected state.

Does interruption recovery work with git-based recovery tools?

Yes, interruption recovery works with git-based recovery tools, integrating directly with git status and git logs to capture snapshots and reconstruct context during restoration.