context-save

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Save working context. Captures git state, decisions made, and remaining work so any future session can pick up without losing a beat. It integrates with commands like /context-save and /context-restore to resume later.

Core Features & Use Cases

  • Save current session state including git status, key decisions, and remaining tasks for a smooth future continuation.
  • Pair with /context-restore to resume exactly where you left off across sessions or machines.
  • Designed to work within the gstack workflow, with an explicit preamble and session management.

Quick Start

Ask me to save your current context with /context-save to resume later using /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 later?

You can save your working context by using the /context-save command to capture your current git state, decisions made, and remaining work. This creates a deterministic savepoint with local persistence for seamless future continuation.

What is the best way to resume a development session across different machines?

The best way to resume a development session across machines is to use /context-restore. It restores your saved git state, key decisions, and remaining tasks so you can pick up exactly where you left off without losing progress.

Can I use context-save within the gstack workflow for session management?

Yes, context-save is designed to work within the gstack workflow. It uses an explicit preamble and session management to capture your current state, ensuring seamless continuation across hold-and-resume scenarios.

Does context-save work without any external dependencies or components?

Yes, context-save operates without external dependencies or components. It implements a deterministic savepoint flow using local persistence to capture your git state and decisions for future session restoration.

When do I need to save context during a software engineering project?

You need to save context during a software engineering project when you want to pause work and resume it in a future session. This captures your current git state and remaining tasks to prevent losing progress across sessions or devices.

How does a deterministic savepoint flow handle local persistence for session state?

A deterministic savepoint flow handles local persistence by systematically capturing your git state, decisions made, and remaining work. This dedicated restore path ensures your session state is reliably saved and seamlessly continued later.