context-save

Capture git state, decisions, and remaining work for session resumption.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Save working context by capturing git state, decisions made, and remaining work so future sessions can resume without losing momentum.

Core Features & Use Cases

  • Save and persist current session state, including branch, status, and decisions.
  • Pair with /context-restore to resume later across sessions and branches.

Quick Start

Save the current session context now and resume later with context-restore to continue exactly where you left off.

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 workflow context to resume work later?

You can save your git session context by capturing the current branch, status, and decisions into a persistent checkpoint, ensuring continuity across multiple sessions and branches without losing momentum.

What is a git session checkpoint and how does it work?

A git session checkpoint records your working context, including branch state and decisions, without modifying code. It integrates with restoration workflows to ensure reliable backtracking and seamless session continuity.

Can I restore my working context across different git branches and sessions?

Yes, you can restore working context across different git branches and sessions. The Skill applies saved state and prompts across branches, ensuring continuity even after interruptions.

Does saving my working context modify my actual git state or code?

Saving your working context does not modify your code. The Skill only records the current git state, decisions, and remaining work, leaving your actual repository untouched during the checkpoint process.

What's the best way to preserve decisions and remaining work before an interruption?

The best way to preserve decisions before an interruption is to run a context-save checkpoint. This captures your git state and remaining tasks, pairing with context-restore to resume exactly where you left off.