context-save

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

2|Updated May 8, 2026
One-click install
npx skills add https://github.com/xotong/claude-marketplace --skill context-save-xotong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-save
Source: https://github.com/xotong/claude-marketplace/tree/main/plugins/gstack/skills/context-save
Command: npx skills add https://github.com/xotong/claude-marketplace --skill context-save-xotong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Save and preserve your current working context, including git state and decisions, so you can resume later without losing track.

Core Features & Use Cases

  • Snapshot git state (branch, uncommitted changes) and the list of decisions made, along with the remaining work, to enable precise context restoration.
  • Pair with /context-restore to resume exactly where you left off across sessions and different devices.
  • Supports multi-session planning and debugging by maintaining intent and next steps for a smoother workflow.

Quick Start

Run /context-save to snapshot your current git state, decisions, and remaining 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 before pausing a troubleshooting session?

To save your working context before pausing a troubleshooting session, you can snapshot your current git state, recorded decisions, and remaining work to ensure precise reproducibility later.

What is the best way to preserve git branch state and decisions for multi-session debugging?

The best way to preserve git branch state and decisions for multi-session debugging is to capture uncommitted changes and remaining work, maintaining intent across sessions and different devices for a smoother workflow.

Can I resume a refactoring session exactly where I left off after closing my IDE?

Yes, you can resume a refactoring session exactly where you left off by pairing this context snapshot with a restore command, picking up the preserved git state and next steps seamlessly.

Does capturing git state for context restoration require committing uncommitted changes?

Capturing git state for context restoration does not require committing uncommitted changes, as it snapshots your current branch state and working decisions directly to enable precise context restoration later.

When do I need to snapshot my working context during a development workflow?

You need to snapshot your working context during a development workflow whenever pausing, refactoring, or starting a new troubleshooting session to ensure reproducibility and prevent losing track of decisions.