context-save

Save git state and session summaries into gstack-managed artifacts.

1|Updated May 5, 2026

Search Tags:#git #context #checkpoint #decision capture #project continuity #session state #resume workflow

Ready to run

npx skills add https://github.com/yashs33244/my-mac-claude --skill context-save-yashs33244

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: context-save
Source: https://github.com/yashs33244/my-mac-claude/tree/main/skills/gstack/context-save
Command: npx skills add https://github.com/yashs33244/my-mac-claude --skill context-save-yashs33244

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

context-save helps you preserve the live state of your work (like the current git branch and what you decided) so you can stop, switch tasks, or hand off to a future session without losing momentum.

Core Features & Use Cases

Captures working context: records git state, key decisions made, and remaining work so a later session can continue with less re-explaining.
Works as a checkpoint for continuity: use it when you are asked to “save progress” or “save state,” then pair it later with /context-restore to resume.
Avoids the common restart tax: reduces the chance the AI forgets what was already tried, why choices were made, or what’s left.

Quick Start

Ask the AI: “Save my current progress and context, including what I decided and what remains, so I can resume later with /context-restore.”

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 working context and git state to resume a project later?▼

To save your working context, record the current git branch, key decisions, and remaining tasks into session artifacts. This checkpoint preserves your project continuity so a future session can resume without re-explaining previous work.

What is the best way to capture decisions and remaining work for long-running projects?▼

Capturing decisions and remaining work involves creating a structured summary of your current session state alongside git details. This prevents the restart tax where an AI forgets what was already tried, ensuring smooth workflow continuity across interrupted tasks.

Can I use context checkpoints with plan-mode safe operations?▼

Yes, context checkpoints support plan-mode safe operations by recording your current git state and structured summary into managed session artifacts. This ensures your workflow state is preserved securely without disrupting active plan execution.

How do I resume a workflow after saving my session state?▼

Resuming a workflow after saving session state requires pairing the saved checkpoint with a restore operation. The recorded git state and decision summary provide the necessary continuity to pick up remaining tasks without losing momentum.

When should I create a checkpoint to save my progress?▼

Create a checkpoint when asked to save progress or state, when switching tasks, or when handing off to a future session. This avoids losing decisions and remaining work, reducing the chance of forgetting why specific choices were made.

Does saving project context require any external dependencies?▼

Saving project context requires no external dependencies. It records git state and a structured summary of decisions directly into managed session artifacts, functioning independently within your existing software engineering workflow.