context-restore

Restore saved state and context across branches after session handoffs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/simbotNL/BT --skill context-restore-simbotnl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-restore
Source: https://github.com/simbotNL/BT/tree/main/plugins/gstack/context-restore
Command: npx skills add https://github.com/simbotNL/BT --skill context-restore-simbotnl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill restores the most recent saved state from previous sessions, allowing you to pick up where you left off, even across workspace handoffs.

Core Features & Use Cases

  • State Restoration: Loads the most recent saved state, ensuring you can resume work from where you last stopped.
  • Session Persistence: Preserves all context, including project settings, variables, and progress.
  • Cross-Branch Compatibility: Restores states across all branches by default, offering flexibility for different workflows.

Quick Start

Run the 'context-restore' Skill to resume your last saved state.

Frequently Asked Questions about context-restore

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

FAQPage Schema
How do I restore working context from a previous session after a workspace handoff?

Restoring working context from a previous session is achieved by loading the most recent saved state, allowing you to seamlessly resume workflows and pick up exactly where you left off after workspace handoffs.

What is session persistence and how does it preserve project variables?

Session persistence preserves all context, including project settings, variables, and progress. This ensures that your entire working environment is saved and can be fully restored when you resume your work.

Can I resume a workflow across different branches without losing state?

Yes, you can resume workflows across different branches without losing state. The context restoration process offers cross-branch compatibility by default, restoring states across all branches for flexible collaboration.

What is the best way to manage state resumption for multi-branch collaboration?

The best way to manage state resumption for multi-branch collaboration is to use a context restoration process that applies to environments requiring consistent context preservation across all branches by default.

Do I need any specific dependencies to enable workflow resumption?

No specific dependencies are required to enable workflow resumption. You can run the context restore process directly in your environment to load your most recent saved state and resume work.