session-recovery

Locate and resume interrupted Copilot CLI sessions from session_store history.

18|3|Updated Jul 3, 2020
One-click install
npx skills add https://github.com/jguadagno/jjgnet-broadcast --skill session-recovery-jguadagno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-recovery
Source: https://github.com/jguadagno/jjgnet-broadcast/tree/main/.agents/skills/session-recovery
Command: npx skills add https://github.com/jguadagno/jjgnet-broadcast --skill session-recovery-jguadagno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables users to identify and resume interrupted Copilot CLI sessions, preventing loss of ongoing work due to crashes or network issues.

Core Features & Use Cases

  • Session Identification: Query recent and relevant session histories from the session_store database.
  • Context Inspection: Retrieve detailed session activities, checkpoints, and related files to assess progress.
  • Resume Workflow: Facilitate quick recovery by resuming previous sessions with minimal manual effort.
  • Use Case: For example, if a termainal crash occurred while editing a pull request, this Skill helps locate that session and continue work without starting over.

Quick Start

Ask the AI to find recent sessions related to your current project directory and resume the one with ongoing work.

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 terminal crash?

To resume an interrupted Copilot CLI session, query the session_store database to locate recent histories and retrieve context. This restores your workflow by resuming previous command-line tasks without starting over.

How does Copilot CLI session recovery work when restoring lost work?

Session recovery works by querying session history and context from the session_store database. It retrieves detailed session activities, checkpoints, and related files to assess progress before safely resuming the interrupted workflow.

Can I find a specific Copilot CLI session history related to my current project directory?

Yes, you can find specific Copilot CLI session histories by querying the session_store database for recent sessions related to your current project directory. This allows targeted resumption of ongoing work.

What is the best way to recover a Copilot CLI session after network issues?

The best way to recover a Copilot CLI session after network issues is to use session recovery to query the session_store. It identifies the interrupted session and facilitates quick recovery with minimal manual effort.

Do I need a database to restore interrupted Copilot CLI sessions?

Yes, restoring interrupted Copilot CLI sessions requires the session_store database. This database stores the session history, activities, and checkpoints necessary to locate and safely resume previous workflows.