checkpoint-management
Scannednpx machina-cli add skill a5c-ai/babysitter/checkpoint-management --openclawCheckpoint Management
Overview
Git-backed checkpoint system providing safe rollback points during development sessions. Each checkpoint creates a tagged commit with descriptive metadata for easy identification and restoration.
Operations
Create Checkpoint
- Stage all current changes
- Create commit with [CHECKPOINT] prefix
- Tag with claudekit-checkpoint-{timestamp}
- Record metadata: files changed, insertions, deletions
Restore Checkpoint
- List available checkpoints by tag
- Preview changes that would be reverted
- Restore to selected checkpoint via git reset
- Verify restored state matches checkpoint
Session Isolation
Checkpoints are session-scoped. Tags created during a session can be cleaned up without affecting other work.
When to Use
- Before risky refactoring operations
- After passing quality checks (safety checkpoints)
- At the start and end of ClaudeKit sessions
- Before spec execution phases
Processes Used By
claudekit-orchestrator(session start/end checkpoints)claudekit-safety-pipeline(safety checkpoints after quality checks)
Source
git clone https://github.com/a5c-ai/babysitter/blob/main/plugins/babysitter/skills/babysit/process/methodologies/claudekit/skills/checkpoint-management/SKILL.mdView on GitHub Overview
Checkpoint Management provides a Git-backed system to create safe rollback points during ClaudeKit sessions. Each checkpoint stages all changes, commits with a [CHECKPOINT] prefix, and tags the commit with claudekit-checkpoint-{timestamp}, while recording metadata like files changed, insertions, and deletions.
How This Skill Works
You stage all current changes, create a commit with the [CHECKPOINT] prefix, and tag the commit with claudekit-checkpoint-{timestamp}. Checkpoints are session-scoped; you can list them by tag, preview what would be reverted, and restore with git reset, then verify the restored state matches the checkpoint.
When to Use It
- Before risky refactoring operations
- After passing quality checks (safety checkpoints)
- At the start of ClaudeKit sessions
- At the end of ClaudeKit sessions
- Before spec execution phases
Quick Start
- Step 1: git add -A
- Step 2: git commit -m "[CHECKPOINT] describe changes" && git tag claudekit-checkpoint-$(date +%s)
- Step 3: To restore, list checkpoints with git tag -l 'claudekit-checkpoint-*' and then git reset --hard claudekit-checkpoint-<timestamp>; verify with git status and git diff
Best Practices
- Stage all changes with git add -A before creating a checkpoint
- Use descriptive checkpoint messages and include a timestamp in the tag
- Record and review metadata (files changed, insertions, deletions)
- Keep checkpoints session-scoped and clean up unused tags regularly
- Verify restoration by checking git status and diffs after reset
Example Use Cases
- A development session before refactoring a module
- After passing a quality gate to capture a safety checkpoint
- At the start of a ClaudeKit session to capture the initial state
- Before running a heavy spec or test suite
- During a troubleshooting session to isolate changes
