Skill1.3k repo starsupdated today

checkpoint-management

Checkpoint-management provides git-backed state preservation during development work by creating tagged commits with metadata before and after significant operations. Use this skill before executing risky refactors, after passing quality checks, or at session boundaries to enable safe rollback to known good states without affecting parallel work.

View source Repository: babysitter

Install in Claude Code

Copy

git clone --depth 1 https://github.com/a5c-ai/babysitter /tmp/checkpoint-management && cp -r /tmp/checkpoint-management/library/methodologies/claudekit/skills/checkpoint-management ~/.claude/skills/checkpoint-management

Then start a new Claude Code session; the skill loads automatically.

Definition

SKILL.md

# Checkpoint 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)