context-restore

Restore the most recently saved working context across branches.

Updated May 14, 2026
One-click install
npx skills add https://github.com/lemig/transcriptor --skill context-restore-lemig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-restore
Source: https://github.com/lemig/transcriptor/tree/main/.claude/skills/gstack/context-restore
Command: npx skills add https://github.com/lemig/transcriptor --skill context-restore-lemig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restores the most recently saved working context across branches so you can pick up where you left off, even after workspace handoffs.

Core Features & Use Cases

  • Loads the latest saved state via /context-save, across all branches by default.
  • Supports quick resumption commands like "resume", "restore context", "where was i", or "pick up where i left off" to continue work with minimal friction.
  • Works within Conductor workspaces and across branches to maintain continuity in long-running sessions.

Quick Start

Say "resume" or "restore context" to load your most recent saved state and continue where you left off.

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 branches in a development session?

Yes, you can resume work across different Conductor workspaces. The context-restore skill loads the latest saved state across all branches by default, enabling seamless handoffs and maintaining continuity in long-running sessions between workspaces.

How do I pick up where I left off in a long-running coding session?

To pick up where you left off in a long-running session, simply type "pick up where i left off" or "where was i". The skill retrieves your most recent checkpoint saved via /context-save and restores that working state automatically.

Do I need to save my session state before I can restore my working context?

Yes, restoring context requires a previously saved state. You must use the /context-save command to checkpoint your current working state first, which context-restore then loads to resume your session seamlessly across branches.

What is the best way to resume a checkpointed workflow across multiple branches?

The best way to resume a checkpointed workflow across branches is using context-restore. It automatically fetches the latest saved state across all branches by default, ensuring you continue your work without manually tracking which branch held the most recent session data.

Why does my context restore load a state from a different branch than expected?

Context restore loads the latest saved state across all branches by default, not just the current one. If you saved state on another branch more recently, it will load that checkpoint to ensure the most up-to-date working context is restored.