context-save

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding sessions lose all working context when they end, forcing you to re-explain decisions, branch state, and unfinished work every time you return. This Skill snapshots your current progress so any future session can resume exactly where you left off. ## Core Features & Use Cases - Context Snapshotting: Captures git branch state, decisions made during the session, and remaining work items into a persistent record. - Session Handoff: Pairs with the /context-restore skill so a later session (or a different machine) can reload the saved state without manual notes. - Environment Awareness: Runs a preamble that detects repo mode, session kind (interactive, headless, or spawned), and gstack configuration before saving. - Use Case: Before ending a long refactoring session on a feature branch, invoke the skill to record what was changed, why, and what remains, then resume the next day with /context-restore. ## Quick Start Ask the agent to save my current progress and working context so I can resume this session later.

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 AI coding session progress?

Invoke the context-save skill before ending your session. It captures the current git branch state, decisions made, and remaining work into a persistent record that a future session can reload.

How do I resume a saved session after context-save?

Use the companion /context-restore skill in a new session. It reads the snapshot written by context-save and restores the branch state, decisions, and outstanding work items.

Does context-save work in headless or CI environments?

Yes, the preamble detects the session kind (interactive, headless, or spawned) and adjusts behavior. In headless runs it skips interactive prompts and proceeds without blocking on user questions.

Why was the checkpoint skill renamed to context-save?

Claude Code treats /checkpoint as a native rewind alias in current environments, which shadowed the skill. It was renamed to context-save to avoid the naming conflict.

What are the limitations of saving session context this way?

The snapshot records git state, decisions, and remaining work, but it does not preserve the full conversation history or uncommitted in-memory reasoning. It depends on the gstack toolchain being installed and configured.