checkpoint

/checkpoint — Progress Checkpoints

Create, verify, or list named progress checkpoints. Each checkpoint captures a git snapshot, file state, and test status.

Modes

Mode	Usage	What It Does
create	/checkpoint create core-done	Snapshot current state as a named checkpoint
verify	/checkpoint verify core-done	Compare current state against a checkpoint
list	/checkpoint list	Show all checkpoints with status

Typical Flow

feature-start → core-done → tests-pass → refactored → pr-ready

Instructions

Step 1: Parse Arguments

From $ARGUMENTS, determine:

• Mode: create, verify, or list (default: create if a name is given, list if no arguments)
• Checkpoint name: Kebab-case identifier (e.g., core-done, tests-pass)

Step 2: Ensure Directory

mkdir -p .planning/checkpoints

Step 3: Execute Mode

Mode: CREATE

1. Capture git state:

git rev-parse HEAD
git status --short
git diff --stat

1. Capture file manifest:

# List all tracked files with their hashes
git ls-files -s | head -100

1. Run tests and record status:

# Auto-detect and run
if [ -f "package.json" ]; then npm test 2>&1 | tail -10; fi
if [ -f "pyproject.toml" ]; then pytest 2>&1 | tail -10; fi
if [ -f "Cargo.toml" ]; then cargo test 2>&1 | tail -10; fi

1. Save checkpoint to .planning/checkpoints/[name].md:

---
name: [checkpoint-name]
created: [ISO timestamp]
commit: [git hash]
branch: [branch name]
tests: pass|fail|skip
dirty_files: [count]
---

# Checkpoint: [name]

## Git State
- **Commit:** [hash]
- **Branch:** [branch]
- **Clean:** yes/no
- **Dirty files:** [list if any]

## Test Status
- **Result:** PASS / FAIL / SKIPPED
- **Details:** [summary]

## Files Snapshot
[List of key files and their git hashes at this point]

## Notes
[Any context about what this checkpoint represents]

1. Present confirmation:

## Checkpoint Created: [name]
- **Commit:** [short hash]
- **Tests:** PASS/FAIL
- **Files tracked:** [count]
- **Stored at:** `.planning/checkpoints/[name].md`