context-save

Capture git state, decisions, and remaining work into .gstack context files.

2|1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/vnmoorthy/Skylog --skill context-save-vnmoorthy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-save
Source: https://github.com/vnmoorthy/Skylog/tree/main/.claude/skills/gstack/context-save
Command: npx skills add https://github.com/vnmoorthy/Skylog --skill context-save-vnmoorthy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Saves the current working context by capturing git state, decisions made, and remaining work so you can resume exactly where you left off.

Core Features & Use Cases

  • Capture and persist your session context, including the repository state and decisions.
  • Pair with /context-restore to resume sessions across branches or machines without losing progress.
  • Works across multiple projects and sessions, keeping your workflow coherent.

Quick Start

Ask /context-save to capture your current work state, and later run /context-restore to resume where you left off.

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 to resume a coding session later?

To save your working context, invoke the /context-save command to capture the current git state, decisions made, and remaining work into the local .gstack directory for future session resumption.

Can I resume a git workflow across different branches or machines?

Yes, you can resume a git workflow across different branches or machines by running /context-restore, which retrieves the persisted session state from the .gstack directory to ensure workflow continuity.

What is the best way to capture git state and decisions before pausing a planning session?

The best way to capture git state and decisions before pausing a planning session is using /context-save, which persists repository details and remaining work locally to prevent progress loss.

Do I need gstack installed locally to save and restore my session context?

Yes, you need the gstack context-save tooling installed locally because the implementation relies on it to store working session state directly in your home directory under the .gstack folder.

Does context-save track multiple projects and sessions simultaneously?

Yes, context-save works across multiple projects and sessions, capturing and persisting the specific repository state for each to keep your entire workflow coherent when switching contexts.

Why does my saved session context not restore my exact working progress?

If your saved session context does not restore exact working progress, ensure you are invoking /context-restore in the correct environment, as it depends on retrieving the git state previously stored in the .gstack directory.