checkpoint

Capture git branch, changes, and decisions into stored checkpoints.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Save and resume your working state by capturing the current git state, decisions made, 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 checkpoints with git state, decisions, and remaining work for later resumption.
  • Resume sessions quickly without re-creating decisions when returning to a task.
  • Works across Conductor workspace handoffs between branches.

Quick Start

Run /checkpoint save [title] to capture your current state for easy resumption later.

Frequently Asked Questions about checkpoint

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

FAQPage Schema
How do I save my git workflow context before switching branches?

You can save your git workflow context by running a save command to capture the current branch, staged and unstaged changes, and key decisions. This enables quick session resumption later without losing your working state or recreating previous decisions.

What is the best way to resume a git session across workspace handoffs?

Resuming a git session across workspace handoffs is best handled by retrieving a saved checkpoint. The checkpoint stores your working state, including the git branch and timestamp metadata, enabling you to pick up exactly where you left off.

Can I add titles and notes when saving my git working state?

Yes, you can add optional titles and notes when saving your git working state. This feature allows you to describe the checkpoint with specific context, making it easier to identify and retrieve the correct session for quick handoffs across Conductor workspace branches.

Does the checkpoint system work with Conductor workspace branches?

Yes, the checkpoint system is specifically designed for quick handoffs across Conductor workspace branches. It saves and resumes your working state by capturing the current git branch, staged changes, and key decisions to support seamless context switching.

Where are my git session checkpoints stored for later retrieval?

Your git session checkpoints are stored locally under the ~/.gstack/projects/$SLUG/checkpoints directory. Each checkpoint includes metadata such as the branch name and timestamp, ensuring easy retrieval and quick resumption of your work state.