checkpoint

Capture and serialize workspace state into a project-scoped checkpoint file.

Updated Jul 3, 2025
One-click install
npx skills add https://github.com/andrew-t-james/dotfiles --skill checkpoint-andrew-t-james
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: checkpoint
Source: https://github.com/andrew-t-james/dotfiles/tree/main/dot_claude/skills/checkpoint
Command: npx skills add https://github.com/andrew-t-james/dotfiles --skill checkpoint-andrew-t-james

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables you to preserve the full working context of a project, including branch, git status, recent commits, and uncommitted changes, so you can resume exactly where you left off later.

Core Features & Use Cases

  • Save and serialize the current workspace state into a checkpoint file that can be loaded on a different branch or after a break.
  • Resume from a saved checkpoint to restore branch, status, diffs, and the decision history, ensuring continuity across sessions.
  • List, load, and verify checkpoints to manage long-running work across Conductor workspaces.
  • Support plan-mode workflows by keeping structured progress, working notes, and timestamped context for audits.

Quick Start

Save your current working state with /checkpoint to capture branch, status, and recent changes.

Frequently Asked Questions about checkpoint

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

FAQPage Schema
How do I save git workflow state and resume work on a different branch?▼

You can save git workflow state by serializing your current branch, git status, diffs, and recent commits into a checkpoint file. This checkpoint can later be loaded on a different branch to restore your exact working context and continue work seamlessly.

What is a workspace checkpoint and when do I need to use it?▼

A workspace checkpoint is a serialized snapshot of your project's working state, including branch, status, and uncommitted changes. You need it when resuming long-running work across sessions or switching contexts between different branches while preserving continuity.

Can I list and verify saved checkpoints to manage multiple git sessions?▼

Yes, you can list, load, and verify checkpoints to manage long-running work across workspaces. Each checkpoint records a timestamp, title, and modified files, ensuring you can reliably identify and restore the correct session context.

Does saving uncommitted changes and diffs work across different branches?▼

Yes, saving uncommitted changes and diffs works across different branches by capturing the full workspace state into a project-scoped checkpoint. You can apply this saved state later from any branch to resume with your context and modifications preserved.

What's the best way to preserve project context for a plan-mode workflow?▼

The best way to preserve project context for plan-mode workflows is saving a checkpoint that keeps structured progress, working notes, and timestamped context. This ensures continuity and provides an audit trail for long-running tasks.