context-restore

Restore saved working contexts from previous /context-save executions.

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/ericdahl-dev/coauthor-cleaner --skill context-restore-ericdahl-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-restore
Source: https://github.com/ericdahl-dev/coauthor-cleaner/tree/main/.claude/skills/gstack/context-restore
Command: npx skills add https://github.com/ericdahl-dev/coauthor-cleaner --skill context-restore-ericdahl-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The context-restore skill solves the issue of losing your progress on tasks across branches by restoring your previous saved working state, enabling a seamless and efficient continuation of workflows.

Core Features & Use Cases

  • Saved Context Restoration: Retrieve the most recent state of a working context previously saved by the /context-save skill.
  • Cross-Branch Resilience: Work in confidence that any interrupted sessions across branches can be effortlessly picked up again.
  • Default Operation: Trigger with "resume where i left off" or other context restoration keywords for quick return to prior progress.
  • Use Case: Ideal for collaborative or continuous work on multiple branches where maintaining progress and context across sessions is crucial.

Quick Start

To resume your work context, use the 'resume context' command.

Frequently Asked Questions about context-restore

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

FAQPage Schema
How do I resume working context after switching git branches?

To resume working context after switching git branches, you trigger a context restoration command to retrieve your most recent saved state. This enables effortless continuation of interrupted sessions and previous workflows.

What is session recovery for interrupted developer workflows?

Session recovery for interrupted developer workflows is the process of restoring a previously saved working state. It allows developers switching tasks to regain exact prior progress and seamlessly continue coding.

How do I restore a saved development session?

You restore a saved development session by triggering a resume context command. This action retrieves the most recent working state previously saved during your git workflow, returning you directly to prior progress.

Do I need a previous session checkpoint to restore my working context?

Yes, you need a previous session checkpoint created by a context-save execution to restore your working context. The restoration process relies on these saved checkpoints to retrieve interrupted session state across branches.

Can I recover progress across different branches in my git workflow?

Yes, you can recover progress across different branches in your git workflow. The context restoration mechanism provides cross-branch resilience, ensuring interrupted sessions can be effortlessly picked up again regardless of branch switching.