checkpoint

Create and verify code checkpoints using git stash or commit.

26|Updated Apr 13, 2017
One-click install
npx skills add https://github.com/thesimonho/dotfiles --skill checkpoint-thesimonho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checkpoint
Source: https://github.com/thesimonho/dotfiles/tree/main/AI/skills/checkpoint
Command: npx skills add https://github.com/thesimonho/dotfiles --skill checkpoint-thesimonho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and verify checkpoints in your coding workflow to stabilize iteration cycles, reduce rework, and provide a rollback point during development.

Core Features & Use Cases

  • Create a named checkpoint to capture the current state of work.
  • Verify a checkpoint by comparing the current state against the recorded checkpoint.
  • List and manage existing checkpoints; logs are persisted to .claude/checkpoints.log for auditing.
  • Integrate with git by advising stash or commit points while recording checkpoints.

Quick Start

Create a named checkpoint using /checkpoint create <name> to capture your current state.

Frequently Asked Questions about checkpoint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a checkpoint in my git workflow to safely rollback code changes?

You can verify a checkpoint by running the verify operation, which compares your current working state against the previously recorded checkpoint to ensure stability and detect unintended deviations during iterative coding.

Can I use checkpoints to stabilize development workflows in CI pipelines?

Yes, you can manage existing checkpoints using the list operation to view recorded entries and the clear operation to remove them, with all activity persisted to .claude/checkpoints.log for continuous auditing during feature work.

What is the best way to reduce rework during iterative coding and bug fixes?

The best way to reduce rework during iterative coding and bug fixes is to create trusted checkpoints that capture provenance through git stash or commit, providing a stable rollback point if an iteration introduces new defects.

How do I verify a checkpoint against my current working state during feature development?

You can verify a checkpoint by running the verify operation, which compares your current working state against the previously recorded checkpoint to ensure stability and detect unintended deviations during iterative coding.

Does the checkpoint version-control process require any specific dependencies or external components?

No, the checkpoint version-control process requires no external dependencies or components, relying solely on native git stash or commit operations to record provenance and log state changes to .claude/checkpoints.log.