context-restore

Restore the most recent saved working context across git branches and Conductor workspace handoffs.

Updated May 27, 2026
One-click install
npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill context-restore-shmurdoc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-restore
Source: https://github.com/Shmurdoc/EasyRide-v1/tree/main/.opencode/skills/gstack-context-restore
Command: npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill context-restore-shmurdoc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When you switch branches, close your laptop, or hand off work to a teammate, you lose the mental context of what you were building. This Skill eliminates that friction by restoring your most recent saved workspace state — including branch, recent files, and progress notes — so you can resume exactly where you left off without manual reconstruction.

Core Features & Use Cases

  • Cross-Branch Context Restoration: Automatically loads the latest saved state regardless of which git branch you're currently on, so switching contexts never loses history.
  • Workspace Handoff Support: Designed for Conductor environments where work moves between AI sessions; restores the full working state so a new session picks up seamlessly.
  • Proactive Session Management: Tracks active sessions, cleans up stale ones, and surfaces recent artifacts like checkpoints and reviews to accelerate re-entry.

Quick Start

Use the context-restore skill to load your most recent saved session state and resume work on the current branch.

Frequently Asked Questions about context-restore

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

FAQPage Schema
How do I resume work on a git branch after closing my session?

To resume work on a git branch after closing your session, you can restore your most recent saved workspace state. This automatically loads the latest branch context, recent files, and progress notes so you can pick up exactly where you left off.

What is the best way to switch git branches without losing my working context?

The best way to switch git branches without losing your working context is to use a session restoration mechanism. It automatically tracks active sessions and loads the latest saved state regardless of your current branch.

Can I hand off an in-progress task to a teammate in a Conductor workspace?

Yes, you can hand off an in-progress task to a teammate in a Conductor workspace. The context restoration mechanism reconstructs the full project state so a new session picks up seamlessly without manual reconstruction.

Do I need gstack session storage to restore my project state?

Yes, you need gstack session storage to restore your project state. Reconstructing the full working state requires gstack session storage, git branch detection, and timeline artifact indexing to function properly.

How does timeline artifact indexing help when onboarding a teammate?

Timeline artifact indexing helps when onboarding a teammate by surfacing recent artifacts like checkpoints and reviews. This accelerates re-entry into the in-progress task by providing the full working state history.

Why does switching branches cause me to lose my mental context of what I was building?

Switching branches causes you to lose your mental context because standard git operations do not save your workspace state. You need a context restoration mechanism to eliminate this friction and track active sessions across handoffs.