context-save

You can save work progress and git state by running this Skill to capture your current branch, uncommitted changes, and pending work items into a persistent local store. This preserves session decisions so you can resume your development workflow instantly without onboarding overhead.

Pausing a debugging session requires saving your git state and pending work items first. This Skill logs remaining next steps and session decisions to a persistent local store, enabling a paired context-restore workflow to seamlessly resume the mid-task development later with no lost progress.

Yes, context-save requires integration with git repositories and local gstack tooling to function. It captures your current git branch, recent commit history, and uncommitted changes to persist context artifacts for later restoration via the paired context-restore workflow.

Yes, you can track mid-feature development progress across multiple sessions by saving work context. The Skill logs remaining work items and session decisions, ensuring you pick up exactly where you left off with no onboarding overhead when switching between cross-session feature development tasks.

When saving work context for session resume, note that this Skill requires local gstack tooling and a git repository to persist context artifacts. It is specifically designed for paused mid-task workflows like debugging and code review, not for managing non-git or untracked project states.