OpenParable
Skip to content
← Back to skills

Checkpoint Management

Development
checkpoint-management

Checkpoint Management is an Agent Skill for development published in the a5c-ai/babysitter repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Git-backed state management for safe rollback. Create and restore checkpoints with tagged commits and metadata tracking.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/a5c-ai/babysitter/blob/HEAD/library/methodologies/claudekit/skills/checkpoint-management/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/checkpoint-management, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

  • 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)