context-save

Save git state, decisions, and remaining work to a Markdown checkpoint.

1|Updated Apr 6, 2026

Search Tags:#git #workflow #context #save #checkpoint #session

Ready to run

npx skills add https://github.com/zhu637882-stack/jiaoyi --skill context-save-zhu637882-stack

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: context-save
Source: https://github.com/zhu637882-stack/jiaoyi/tree/main/qoder-config-backup/skills/gstack-context-save
Command: npx skills add https://github.com/zhu637882-stack/jiaoyi --skill context-save-zhu637882-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

Snapshot current working context including git state and key decisions to a reusable checkpoint.
Pair with /context-restore to resume work exactly where you left off across sessions and tools.

Quick Start

Run the /context-save command to capture the current working context and store it for later restoration.

Frequently Asked Questions about context-save

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I save git state and session context to resume work later?▼

You can save git state and session context by running the /context-save command, which captures current progress, key decisions, and remaining tasks into a reusable checkpoint. This preserves working state for seamless future restoration.

What is a context checkpoint and when do I need it for my workflow?▼

A context checkpoint is a saved snapshot of your working session that captures git state and decisions. You need it when resuming interactive sessions or automation workflows to prevent losing progress across tools.

Can I restore a saved git checkpoint across different sessions and tools?▼

Yes, you can restore a saved git checkpoint across sessions by pairing the save command with a restore action. This allows you to resume work exactly where you left off, bridging context seamlessly across different tools.

Does the context checkpoint process require any dependencies or components?▼

No, the context checkpoint process requires no dependencies or components. It operates independently to capture session state, relying only on the built-in /context-save command to store progress.

What's the best way to preserve interactive session decisions for automation workflows?▼

The best way to preserve interactive session decisions is to save context to a checkpoint. This captures decisions and git state, allowing automation workflows to resume seamlessly without losing prior progress.

Why does my working context disappear when I start a new git session?▼

Working context disappears in new git sessions because state and decisions are not automatically persisted. Saving context to a checkpoint captures this information so future sessions can resume without losing progress.