restore

Detect stale local state and reload the latest JSON checkpoint to resume interrupted workflows.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/monktui/git-review --skill restore-monktui
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: restore
Source: https://github.com/monktui/git-review/tree/main/.claude/skills/restore
Command: npx skills add https://github.com/monktui/git-review --skill restore-monktui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents lost work and broken workflows by helping you resume after a crash or a new session while avoiding unsafe, automatic deletions.

Core Features & Use Cases

  • Stale State Detection: Detects stale teams, extra git worktrees, and dead tmux panes to understand what remains on disk.
  • User-Gated Cleanup: Removes stale teams and prunes orphaned worktrees only after explicit user confirmation.
  • Checkpoint-Driven Resumption: Reads the most recent checkpoint JSON to show timestamp and progress so you can pick up accurately.
  • Cross-Session Context Retrieval: Searches prior project memory for relevant observations to resume in the right direction.
  • Project Status Reconciliation: Lists incomplete Linear tickets to surface in-progress work that may need continuation.

Quick Start

Ask the assistant to run /resume so it can present a cleanup and checkpoint summary, then ask what exact task to continue next.

Frequently Asked Questions about restore

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

FAQPage Schema
How do I resume a tmux session after a crash without losing work?▼

To resume a tmux session after a crash, this tool detects stale teams and dead panes, reads the latest JSON checkpoint, and presents a progress summary for user-directed next steps. It avoids risky automatic deletions by requesting explicit confirmation before cleaning up orphaned git worktrees.

How do I clean up orphaned git worktrees safely?▼

You can clean up orphaned git worktrees safely through user-gated cleanup, which lists stale teams and extra worktrees but only prunes them after explicit user confirmation. This prevents accidental data loss when restoring interrupted work or cross-session project memory.

How does checkpoint-driven session restore work for AI agent workflows?▼

Checkpoint-driven session restore works by reading the most recent local checkpoint JSON file to display timestamps and progress. It searches prior project memory and checks Linear ticket status to accurately resume AI agent workflows without losing context.

Can I use session restore to check incomplete Linear tickets alongside tmux state?▼

Yes, you can use session restore to check incomplete Linear tickets alongside tmux state. It lists team, worktree, and tmux infrastructure states, reconciles project status by surfacing in-progress Linear tickets, and limits output to a maximum of 3 concurrent agents for safe management.

What are the limitations when restoring multiple concurrent AI agent sessions?▼

A key limitation when restoring concurrent AI agent sessions is a hard limit of a maximum of 3 concurrent agents presented in the summary. Additionally, it requires explicit user confirmation before removing stale local state or pruning orphaned worktrees to prevent unsafe automatic deletions.