context-save

Save git state, decisions, and remaining work to a checkpoint file.

5|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/timurgaleev/vibestack --skill context-save-timurgaleev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-save
Source: https://github.com/timurgaleev/vibestack/tree/main/skills/context-save
Command: npx skills add https://github.com/timurgaleev/vibestack --skill context-save-timurgaleev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Save working context by capturing the git state, decisions made, and remaining work so that a future session can resume without losing progress.

Core Features & Use Cases

  • Save the current session state including branch, unstaged and staged changes, recent history, and a generated summary of decisions and remaining work.
  • Persist a checkpoint file under ~/.vibestack/projects/$SLUG/checkpoints with a sanitized title, timestamp, and session duration for cross-branch restore.
  • List and load saved contexts later with /context-restore to resume work across branches and sessions.

Quick Start

Invoke /context-save with an optional title to create a saved-context entry for the current work.

Frequently Asked Questions about context-save

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

FAQPage Schema
How do I save my git working context to resume a development session later?

To save your git working context, invoke the /context-save command with an optional title. It records the branch, staged and unstaged changes, decisions, and remaining work into an append-only checkpoint file for later resumption.

What is a development session checkpoint and when do I need one?

A development session checkpoint is an append-only record capturing your branch, timestamp, duration, and modified files. You need one before switching context or ending a session to avoid losing progress on complex software engineering tasks.

Can I restore a saved git context across different branches and sessions?

Yes, you can restore a saved git context across different branches and sessions. Checkpoints are stored under a shared project directory, enabling cross-branch continuity when you load them later with /context-restore.

Does saving a context checkpoint modify my actual code or git state?

No, saving a context checkpoint does not modify your code or git state. It strictly derives information from your current git status and conversation history to record decisions and remaining work without performing code changes.

How do I list and load previously saved working contexts?

You list and load previously saved working contexts by using the /context-restore command. This allows you to browse saved checkpoints and resume your software development workflow exactly where you left off.

What is the best way to maintain workflow continuity when pausing software development?

The best way to maintain workflow continuity is to create an append-only checkpoint that captures your git state, recent history, and a summary of decisions. This ensures future sessions can resume without losing progress.