checkpoint

Save and resume git state checkpoints with Markdown files.

2|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/adityasingh2400/SwarmSell --skill checkpoint-adityasingh2400
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checkpoint
Source: https://github.com/adityasingh2400/SwarmSell/tree/main/.claude/skills/checkpoint
Command: npx skills add https://github.com/adityasingh2400/SwarmSell --skill checkpoint-adityasingh2400

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Save and resume working state checkpoints by capturing 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: create a checkpoint of current branch, status, diffs, and recent logs to allow resuming later.
  • Resume: load the most recent checkpoint and restore context so work can continue without rework.
  • Plan and auditing: maintain a structured record of decisions and remaining work to improve handoffs and collaboration.

Quick Start

To save a checkpoint, run /checkpoint save to create a checkpoint for your current work.

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 working state across git branches?

Git session management captures your current branch, status, modified files, and recent logs into a checkpoint file, allowing you to resume work later without rework.

What is the best way to document decisions and remaining work for a code handoff?

Creating a checkpoint provides a structured record of decisions and remaining work by writing a Markdown file with your branch, timestamp, status, and diffs to improve collaboration and handoffs.

How do I create a checkpoint to save my current progress?

Run the /checkpoint save command to create a checkpoint for your current work, which writes a Markdown file under the ~/.gstack/projects/{slug}/checkpoints directory with your session details.

Can I use checkpoint files to restore context after switching branches in Conductor?

Yes, checkpoints apply across Conductor workspace handoffs between branches by loading the most recent checkpoint to restore context so work can continue without rework.

What information is included in a saved session checkpoint?

A saved checkpoint includes your current branch, timestamp, git status, modified files, recent logs, and a summary of decisions made and remaining work in a Markdown file.