checkpoint

Capture git state, changes, commits, and decisions into a portable checkpoint file.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/legotec73/gstack --skill checkpoint-legotec73
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checkpoint
Source: https://github.com/legotec73/gstack/tree/main/checkpoint
Command: npx skills add https://github.com/legotec73/gstack --skill checkpoint-legotec73

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Save and resume your working state by capturing git state, decisions, and remaining work so you can pick up exactly where you left off, even across Conductor workspace handoffs between branches.

Core Features & Use Cases

  • Save and restore checkpoint states including git status, decision logs, and remaining tasks.
  • Proactively suggest when a session is ending or you switch context to maintain continuity.
  • Enable cross-branch session handoffs so you can resume on a different workspace without losing progress.

Quick Start

Use the checkpoint skill to save your current state with /checkpoint save, then resume with /checkpoint resume to continue exactly where you left off.

Frequently Asked Questions about checkpoint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save and resume my git workflow state across different sessions?

To save and resume your git workflow state, you capture the current branch, staged and unstaged changes, recent commits, and decision logs into a portable checkpoint file. This restores your exact working context to continue where you left off in a later session.

What is the best way to preserve working context when switching git branches?

The best way to preserve working context when switching branches is to save a checkpoint that records your modified files and decision log. This enables cross-branch session handoffs, allowing you to resume your progress on a different workspace without losing unsaved work.

Can I restore unstaged and staged changes after closing my workspace?

Yes, you can restore unstaged and staged changes after closing your workspace by resuming from a saved checkpoint. The checkpoint file stores your complete git status and modified files, ensuring your working context is fully recovered when you return.

How do I record decisions and remaining tasks before ending a development session?

You record decisions and remaining tasks before ending a session by saving a checkpoint with a title and timestamp. This captures your decision log alongside your current git state, ensuring future restoration has all the context needed to proceed.

Does saving a checkpoint require committing my unstaged git changes?

Saving a checkpoint does not require committing your unstaged git changes. The checkpoint process reads your current git state and lists modified files directly, capturing both staged and unstaged changes into a portable file without altering your actual git history.