Save and restore git working context across sessions and branches.
npx skills add https://github.com/ClyptAI/Clypt-Backend --skill checkpoint-clyptai
Please help me install this Agent Skill. Skill: checkpoint Source: https://github.com/ClyptAI/Clypt-Backend/tree/main/.agents/skills/gstack/checkpoint Command: npx skills add https://github.com/ClyptAI/Clypt-Backend --skill checkpoint-clyptai
Save and restore complex working context across sessions and branches.
Save your current work state with /checkpoint save and resume later with /checkpoint resume.
High-intent search queries and answers about installing and using this skill.
Save your git working state by capturing branch, status, diffs, and recent logs into a checkpoint. This preserves complex development context across sessions so you can recreate the exact environment later.
Restoring working context across branches is done by resuming from a previously saved checkpoint. This recreates the exact working environment, including branch state and recent activity, for multi-branch experiments and session handoffs.
Yes, you can list and inspect saved checkpoints to review captured branch, status, and diff data. This helps you decide which working environment and plan to restore before resuming your development task.
A checkpoint captures context for long-running development tasks by implementing a deterministic save flow that records git state, status, diffs, recent logs, and context summaries to preserve the exact working environment for handoffs.
Saving and resuming git working state requires no specific dependencies or components. The checkpoint mechanism operates independently to capture git state and context summaries for restoring complex development environments.
Elad73Reads project status and git state to produce a concise session briefing.
andrew-t-jamesCapture and serialize workspace state into a project-scoped checkpoint file.
cegit27Capture and restore git working state with decisions and tasks.
LarryHsiaoSwitch Git branches safely by stashing or temporarily committing uncommitted changes.
