context-save

To save your git state and work context before switching tasks, invoke the context-save skill to snapshot your current git state, decisions made, and remaining work. This captures your session progress so you can resume work instantly later without losing a beat.

The best way to checkpoint a development session for later restoration is using the context-save skill, which persists your git state, decisions, and remaining tasks. It pairs directly with /context-restore to enable a reliable resume via a future activation.

Yes, you need the gstack workflow integration to capture and persist your current work context. The context-save skill requires gstack to snapshot your git state and remaining tasks, supporting triggers like save progress, save state, and context save.

The /checkpoint command does not save your progress because Claude Code treats /checkpoint as a native rewind alias in current environments, which shadows the skill. It was renamed to context-save to avoid this conflict and properly capture your session state.

To resume work instantly after pausing a development session, first use context-save to capture your git state and remaining tasks, then pair it with /context-restore to pick up exactly where you left off and enable seamless restoration.