context-save

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

Updated May 11, 2026
One-click install
npx skills add https://github.com/wodeh/gstack-kimi --skill context-save-wodeh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-save
Source: https://github.com/wodeh/gstack-kimi/tree/main/context-save
Command: npx skills add https://github.com/wodeh/gstack-kimi --skill context-save-wodeh

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.

Core Features & Use Cases

  • Capture git state, decisions, and remaining work to enable seamless restoration.
  • Integrates with plan-mode workflows and supports proactive prompts to guardrail progress.
  • Use Case: after a long planning session, save context and restore later to continue from the exact point.

Quick Start

Save the current working context now to enable a seamless 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 git state and working context before ending a long planning session?

To save git context, this Skill captures your current git state, decisions made, and remaining work into an auditable checkpoint. This prevents lost progress across long-running planning or debugging tasks spanning multiple branches and workstreams.

What is the best way to resume a debugging session across multiple git branches?

The best way to resume a debugging session is using a context checkpoint mechanism that records your previous git state and decisions. You can then rehydrate the exact session later by integrating with a restore command.

How does saving work context prevent lost progress in long-running development tasks?

Saving work context prevents lost progress by capturing your exact decisions and remaining work into a checkpoint. When future sessions begin, this auditable record rehydrates the state, allowing you to pick up without losing a beat.

Can I integrate context checkpoints with plan-mode workflows for proactive progress guardrails?

Yes, this context checkpoint mechanism integrates directly with plan-mode workflows. It supports proactive prompts that guardrail your progress, ensuring that decisions and remaining work are captured during long planning sessions.

Do I need any dependencies to capture git state for a development session checkpoint?

No external dependencies are required to capture git state for a session checkpoint. The mechanism operates independently to record your working context, git state, and decisions for seamless restoration later.

When should I not rely on manual notes for preserving context across multiple workstreams?

You should avoid manual notes for long-running planning or debugging tasks across multiple branches and workstreams. An auditable checkpoint mechanism is required to prevent lost progress and seamlessly rehydrate the exact session state.