session-recovery

Find interrupted Copilot CLI sessions and restore their last work state from session_store history.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/sachinnair90/gitgloss --skill session-recovery-sachinnair90
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-recovery
Source: https://github.com/sachinnair90/gitgloss/tree/main/.copilot/skills/session-recovery
Command: npx skills add https://github.com/sachinnair90/gitgloss --skill session-recovery-sachinnair90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps recover interrupted Copilot CLI work after crashes, network drops, restarts, or accidental window closes, so unfinished tasks can be located and resumed instead of lost.

Core Features & Use Cases

  • Finds recent sessions and identifies the last checkpoint so you can see exactly where work stopped.
  • Filters out automated keep-alive and heartbeat sessions that would otherwise clutter recovery results.
  • Searches by topic, working directory, issues, branches, and linked references to pinpoint the right session.
  • Supports a full pre-resume review by inspecting conversation turns, checkpoints, touched files, and related issue or commit references.

Quick Start

Ask the skill to locate the most recent interrupted Copilot CLI session for a given topic or branch and summarize the last checkpoint so you can resume it.

Frequently Asked Questions about session-recovery

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

FAQPage Schema
How do I resume an interrupted Copilot CLI session after a crash?

To resume an interrupted Copilot CLI session after a crash, locate the orphaned session in your session store using SQLite checkpoint inspection and restore its last known work state to continue your workflow.

What is the best way to find a lost Copilot session by topic or branch?

Finding a lost Copilot session by topic or branch uses FTS5 keyword search within the SQLite session store to pinpoint and filter exact conversation matches for quick recovery.

Can I review touched files and checkpoints before resuming a Copilot session?

Yes, you can review touched files, conversation turns, and linked issue references by inspecting the last checkpoint in the session store before resuming the Copilot CLI workflow.

How do I filter out automated keep-alive sessions when recovering Copilot work?

Filtering out automated keep-alive and heartbeat sessions during Copilot recovery removes background clutter, ensuring only topic-matched or branch-specific interrupted work states are identified.

Does session recovery work with SQLite and FTS5 for finding orphaned workflows?

Yes, session recovery works with SQLite and FTS5 by querying the session store history to identify recent, orphaned, or branch-specific sessions interrupted by crashes or disconnects.