context-save

Saving git session context involves capturing your current working state, active git branch, and session metadata. This automatically snapshots project configurations and pending tasks to ensure seamless workflow continuity and task resumption.

Engineering workflow continuity is the ability to pause work and resume exactly where you left off without re-evaluating project context. You need it when ending your day or switching tasks, ensuring your next session starts with a clear understanding of the current branch and pending work items.

You can capture git branch state and pending tasks by logging your current progress and configuration details. This snapshots the active git branch, session metadata, and active decisions, creating a restorable checkpoint for future session resumption.

Yes, context-save requires access to local gstack configuration files and git repository metadata to function correctly. It uses these inputs to accurately capture your current working state, active branch, and session metadata for engineering workflows.

The best way to resume an engineering session is to invoke a context capture skill before switching tasks. This preserves your engineering state, active plan mode, and pending work items, allowing your next session to start with a clear understanding of the current branch.

Capturing session metadata prevents losing track of complex engineering work by logging active decisions and pending tasks. This ensures that when you switch tasks or end your day, your next session starts with a clear understanding of the current branch and active plan mode.