context-restore

Load the most recent saved working context across branches.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/nhattran998/personal-athlete-agent --skill context-restore-nhattran998
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-restore
Source: https://github.com/nhattran998/personal-athlete-agent/tree/main/.agents/skills/gstack-context-restore
Command: npx skills add https://github.com/nhattran998/personal-athlete-agent --skill context-restore-nhattran998

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restores the most recently saved working context across all branches so you can resume work without losing state, even when handoffs occur between Conductor workspaces.

Core Features & Use Cases

  • Load the latest saved context from any branch to effortlessly resume multi-branch workflows.
  • Load a specific saved context when a title or identifier is provided, or default to the most recent across branches.
  • Present a clear summary of restored artifacts (checkpoints, timelines, notes) while preserving repository integrity unless you approve changes.

Quick Start

Ask me to run /context-restore to load your most recent saved context from any branch.

Frequently Asked Questions about context-restore

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

FAQPage Schema
How do I restore saved working context across different branches?

Restoring saved working context across branches loads the most recent checkpoint, timeline, and notes from any branch, allowing you to resume multi-branch workflows without losing state.

Can I resume a specific checkpoint if I have multiple saved contexts?

Yes, you can resume a specific checkpoint by providing its title or identifier, which loads that exact saved context artifact instead of defaulting to the most recent one across all branches.

Does restoring a context checkpoint alter my current repository state?

Restoring a context checkpoint preserves your repository state; it only presents a summary of artifacts and maintains repository integrity unless you explicitly confirm changes.

What is the best way to resume a workflow after a Conductor handoff?

The best way to resume a workflow after a Conductor handoff is to load the latest saved context across branches, which captures handoff states and restores timelines and notes seamlessly.

How do context restore mechanisms handle checkpoints from other branches?

Context restore mechanisms aggregate the latest saved context from all branches, capturing cross-branch checkpoints and Conductor handoffs to present a unified summary for resuming work.