checkpoint

Save git state, decisions, and remaining work to checkpoint artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Save and resume your working state by capturing git state, decisions made, and remaining work so you can pick up exactly where you left off, even when moving between branches or Conductor workspaces.

Core Features & Use Cases

  • Capture branch, status, diffs, and recent commits to a portable checkpoint.
  • Attach decisions and working notes to a checkpoint for handoffs between teammates or sessions.
  • Restore context later to resume work without re-reading conversations or re-deriving context.

Quick Start

Run /checkpoint save to save your current state.

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 state to resume work in a different session?

To save and resume your git workflow state across sessions, record your current branch, status, diffs, and recent commits into a portable checkpoint artifact. You can then restore this context later to pick up exactly where you left off without re-reading past conversations.

What is the best way to capture working decisions for a git branch handoff?

Capturing working decisions for a git branch handoff involves attaching a narrative of your decisions and remaining work directly to a saved checkpoint. This ties your git state and notes together, allowing teammates or future sessions to resume development with full context.

How does saving a checkpoint help with Conductor workspace handoffs?

Saving a checkpoint helps with Conductor workspace handoffs by writing your development state, including branch status and working decisions, to a portable artifact. Restoring this checkpoint in a new workspace immediately provides the exact context needed to continue development.

Can I use this to restore git context after switching branches?

Yes, you can restore git context after switching branches by reading a previously saved checkpoint. The checkpoint restores your branch state, diffs, and working decisions, allowing you to resume work without needing to re-derive the context from scratch.

Where are my git checkpoint artifacts stored?

Git checkpoint artifacts are stored as files under the ~/.gstack/projects/$SLUG/checkpoints directory. The system writes your branch status, diffs, and working notes to this location and reads them from there to restore your session context.