Skip to main content
command CX Codex

checkpoint — Claude Code command: what it does, how to install

Saves named Git checkpoints during a Claude Code workflow and compares changed files, test results, and test coverage against earlier marks.

MIT ★ 6,739 updated 2026-01-23

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add WorldFlowAI/everything-claude-code
/plugin install everything-claude-code@everything-claude-code
Open on GitHub

What checkpoint does

This command tracks milestones across code edits. When creating a checkpoint, it runs /verify quick to confirm a clean state, makes a git stash or commit, and appends a line with the timestamp, name, and short Git commit hash into .claude/checkpoints.log.

Running verification against a saved mark reads that log entry and inspects differences. The report lists modified files, test pass counts, coverage shifts, and build status. A functional Git repository is mandatory; without it, stash and commit creation will fail immediately.

What it helps with

  • record intermediate code states before complex refactoring
  • inspect test results and test coverage changes against an earlier step
  • view saved checkpoints with timestamps and short Git commit hashes
  • purge older checkpoints while retaining the latest five entries

Example prompts for the agent

  • /checkpoint create "feature-start"
  • /checkpoint verify "core-done"
  • /checkpoint list

How to install checkpoint

1Plugin marketplace

/plugin marketplace add WorldFlowAI/everything-claude-code
/plugin install everything-claude-code@everything-claude-code

2Manually: put the files in place

.claude/commands/checkpoint.md

Call it with /checkpoint. For all projects use ~/.claude/commands/

Questions about checkpoint

How to install checkpoint in Claude Code?

Add the repository via /plugin marketplace add WorldFlowAI/everything-claude-code, then run /plugin install everything-claude-code@everything-claude-code. You can also place the command file directly into .claude/commands/checkpoint.md.

What does the checkpoint command do?

It creates named Git commits or stashes logged in .claude/checkpoints.log, then evaluates file changes, test runs, and test coverage against those marks.

How does the clear argument work?

Calling /checkpoint clear wipes older saved marks from the log, preserving only the five most recent checkpoints.

Source text

checkpoint.md · MIT
# Checkpoint Command

Create or verify a checkpoint in your workflow.

## Usage

`/checkpoint [create|verify|list] [name]`

## Create Checkpoint

When creating a checkpoint:

1. Run `/verify quick` to ensure current state is clean
2. Create a git stash or commit with checkpoint name
3. Log checkpoint to `.claude/checkpoints.log`:

```bash
echo "$(date +%Y-%m-%d-%H:%M) | $CHECKPOINT_NAME | $(git rev-parse --short HEAD)" >> .claude/checkpoints.log
```

4. Report checkpoint created

## Verify Checkpoint

When verifying against a checkpoint:

1. Read checkpoint from log
2. Compare current state to checkpoint:
   - Files added since checkpoint
   - Files modified since checkpoint
   - Test pass rate now vs then
   - Coverage now vs then

3. Report:
```
CHECKPOINT COMPARISON: $NAME
============================
Files changed: X
Tests: +Y passed / -Z failed
Coverage: +X% / -Y%
Build: [PASS/FAIL]
```

## List Checkpoints

Show all checkpoints with:
- Name
- Timestamp
- Git SHA
- Status (current, behind, ahead)

## Workflow

Typical checkpoint flow:

```
[Start] --> /checkpoint create "feature-start"
   |
[Implement] --> /checkpoint create "core-done"
   |
[Test] --> /checkpoint verify "core-done"
   |
[Refactor] --> /checkpoint create "refactor-done"
   |
[PR] --> /checkpoint verify "feature-start"
```

## Arguments

$ARGUMENTS:
- `create <name>` - Create named checkpoint
- `verify <name>` - Verify against named checkpoint
- `list` - Show all checkpoints
- `clear` - Remove old checkpoints (keeps last 5)

© Affaan Mustafa · MIT · WorldFlowAI/everything-claude-code

Similar slash commands

All slash commands for Git and GitHub →

From the same set29

The whole set →
performance performance — a Claude Code rule that matches model to task and keeps heavy refactors away from the tail of the context window. CX Codex +1 ★ 6,739repo stars coding-style coding-style is a Claude Code rule for code structure and quality checks. It applies while an agent writes or changes code. CX Codex +1 ★ 6,739repo stars hooks The hooks rule defines actions before and after tool calls, plus a final session check. It helps run code checks and review Git-related changes. CX Codex +1 ★ 6,739repo stars agents Defines nine agents in ~/.claude/agents/ for different development tasks: planning, design, testing, code review, and more. Run them in parallel for independent work. CX Codex +1 ★ 6,739repo stars learn The learn slash command turns reusable lessons from the current session into skills. Run it after a difficult fix, debugging session, or project-specific discovery. CX Codex +1 ★ 6,739repo stars setup-pm setup-pm — a command to configure which package manager (npm, pnpm, yarn, or bun) Claude Code uses in your project or globally. Use it when you want to enforce a specific manager across your workflow. CX Codex +1 ★ 6,739repo stars code-reviewer The code-reviewer subagent reviews code changes for security vulnerabilities, bugs, performance problems, and style violations. Run it immediately after writing or modifying code to catch issues before they reach production. CX Codex ★ 6,739repo stars planner planner generates structured implementation plans and refactoring roadmaps for Claude Code projects. CX Codex ★ 6,739repo stars

Project sponsors

Companies that keep this analytics open