context-save

To save your working context, this skill captures your current git state, decisions made, and remaining tasks into a restorable snapshot. You trigger it by asking to "save progress" or "save state," ensuring future sessions resume without losing a beat.

The best way to resume work is pairing this skill's saved state with the /context-restore command. While this skill persists your git state and remaining tasks, /context-restore loads that snapshot to seamlessly pick up your long-running project.

Yes, context-save works alongside other gstack utilities to maintain continuity in long-running projects. It functions as a standalone progress tracker within your workflow, requiring no external dependencies to capture and persist your session data.

The checkpoint skill was renamed to context-save because Claude Code treats /checkpoint as a native rewind alias, which was shadowing the skill. The rename ensures the save state trigger functions correctly without conflicting with built-in environment commands.

You restore a saved session by using the /context-restore command, which loads the git state, decisions, and remaining work previously captured by context-save. This combination allows you to seamlessly resume work across different development environments.

Yes, you can use context-save without external dependencies because it operates entirely within your environment using standard instructions. It requires no additional components or libraries to capture your working context and prepare it for restoration.