context-save

To save your git state and session context, trigger a snapshot that captures your current branch, staged changes, and remaining work items. This records your exact development progress so you can seamlessly resume the session after an interruption or restart.

A git session checkpoint is a captured snapshot of your current branch, staged changes, and decision log. It preserves your work context by recording these elements alongside remaining tasks, enabling precise restoration of your development environment later.

Yes, you can restore a previous git session across different branches and interruptions. By pairing the saved context snapshot with a restoration command, the system recreates your previous session state, including branch context and pending work items.

You can record decisions and remaining work items by executing a context save command before switching git branches. This captures an ordered log of your choices and pending tasks, ensuring no progress is lost when you context-switch.

Yes, context-save works without external dependencies or npm packages. It operates using Bash-based actions and prompts integrated directly into your environment, requiring only a frontmatter-defined entry to function.

You should use a session checkpoint instead of standard git commits when you need to preserve unfinished work, mental context, and pending decisions across interruptions. Unlike commits, it captures your full working state and remaining tasks for seamless later resume.