session-recovery

Query SQLite session_store to recover and resume Copilot CLI sessions.

41|8|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/tamirdresher/squad-skills --skill session-recovery-tamirdresher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-recovery
Source: https://github.com/tamirdresher/squad-skills/tree/main/plugins/session-recovery
Command: npx skills add https://github.com/tamirdresher/squad-skills --skill session-recovery-tamirdresher

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you find and resume recently closed or interrupted Copilot CLI sessions, preventing data loss and saving you from having to restart your work.

Core Features & Use Cases

  • Resume Interrupted Work: Quickly get back to a previous coding session that was accidentally closed.
  • Find Past Sessions: Search for sessions based on keywords, working directory, or time range.
  • Review Session History: Examine conversation turns, checkpoints, and files touched in past sessions before resuming.
  • Use Case: You were working on a complex feature, your terminal crashed, and you need to pick up exactly where you left off. This skill helps you find that session and resume it.

Quick Start

Use the session recovery skill to find and resume my most recent Copilot CLI session.

Frequently Asked Questions about session-recovery

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

FAQPage Schema
How do I recover a lost Copilot CLI session after my terminal crashes?

To recover a lost Copilot CLI session, this skill queries the SQLite session_store database to retrieve session metadata. It locates interrupted or recently closed workflows by matching working directories, topics, or time ranges, allowing you to resume work directly.

Can I search for past Copilot CLI sessions by working directory or topic?

You can search past Copilot CLI sessions by working directory, topic, or time range. The skill executes SQL queries against the session history database to filter and retrieve the exact conversation turns and checkpoints you need.

How do I review conversation history and touched files before resuming a Copilot CLI session?

Reviewing conversation history and touched files before resuming a Copilot CLI session is done by querying the SQLite database. The skill extracts and presents details on past conversation turns, checkpoints, and modified files so you can verify your previous state.

Does session recovery require a SQLite database to find interrupted Copilot CLI workflows?

Session recovery requires the SQLite session_store database to find interrupted Copilot CLI workflows. It relies entirely on executing SQL queries against this database to retrieve the session metadata needed for resuming your work.

What is the best way to resume recently closed Copilot CLI sessions without losing data?

The best way to resume recently closed Copilot CLI sessions without losing data is to query the SQLite session history. This approach retrieves conversation turns and checkpoints, preventing data loss and saving you from restarting your workflow.