context-restore

Restores the most recent saved context across branches and Conductor workspaces via shell commands and allowed tools.

12|6|Updated Dec 2, 2025
One-click install
npx skills add https://github.com/shogo-labs/shogo-ai --skill context-restore-shogo-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-restore
Source: https://github.com/shogo-labs/shogo-ai/tree/main/packages/agent-runtime/templates/virtual-engineering-team/.shogo/skills/gstack-context-restore
Command: npx skills add https://github.com/shogo-labs/shogo-ai --skill context-restore-shogo-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restore the user's working context saved earlier by /context-save and load the most recent state across all branches so you can pick up where you left off — even across Conductor workspace handoffs.

Core Features & Use Cases

  • Restore the most recent saved context across branches to maintain continuity during rapid work across forks.
  • Seamlessly resume work after interruptions, space switches, or Conductor handoffs without re-creating state.
  • Works with the /context-save workflow to guarantee deterministic context loading.

Quick Start

Invoke the restore command to load the most recent saved context from /context-save.

Frequently Asked Questions about context-restore

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

FAQPage Schema
How do I restore my working context after switching Conductor workspaces?

To restore your working context, invoke the restore command to deterministically load the most recent state saved by /context-save. This instantly re-establishes your cross-branch continuity and lets you resume work seamlessly across different Conductor workspaces.

What is cross-branch context restoration and when do I need it?

Cross-branch context restoration is the process of loading your latest saved working state across multiple repository forks. You need it to maintain continuity when rapidly switching branches or resuming development after unexpected interruptions.

How do I resume a session after an interruption without recreating state?

You can resume a session after interruptions by loading the most recent saved context. The restore mechanism locates the latest state captured by /context-save and deterministically applies it to your current workspace.

Does context restore work with sessions saved across different forks?

Yes, context restore works across different forks. It loads the most recent state across all branches, ensuring you can pick up exactly where you left off without re-creating state during Conductor workspace handoffs.

Do I need a previously saved session to use context restore?

Yes, you need a previously saved session to use context restore. It functions by locating and loading the working context captured earlier by the /context-save command to guarantee deterministic context loading.