make-checkpoint

Create timestamped checkpoint folders with status summaries and diffs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/cychen2021/claude-skills --skill make-checkpoint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: make-checkpoint
Source: https://github.com/cychen2021/claude-skills/tree/main/make-checkpoint
Command: npx skills add https://github.com/cychen2021/claude-skills --skill make-checkpoint

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Create timestamped checkpoints to capture a current codebase state for structured review.

## Core Features & Use Cases

  • Generates a timestamped checkpoint folder under checkpoints/ containing a status summary, a diff from the previous checkpoint, and tailored review guidelines for both documentation and code.
  • Determines the previous checkpoint, creates the new cp-<timestamp> directory, and writes status-quo.md, diff-vs-<previous>.md, doc-review-guidelines.md, and code-review-guidelines.md.
  • Supports a consistent workflow for computing a YYMMDD timestamp and organizing repository state for comparison and review.

### Quick Start Run the Make Checkpoint skill to generate a new checkpoint for the current repository state.

Frequently Asked Questions about make-checkpoint

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

FAQPage Schema
How do I create a timestamped checkpoint of my codebase for structured review?

To create a timestamped checkpoint, run the Make Checkpoint skill to capture your current repository state, generating a status summary, a diff against the previous checkpoint, and tailored review guidelines.

What files are generated when I create a code checkpoint?

Creating a code checkpoint generates a new timestamped directory containing status-quo.md, a diff-versus-previous.md file, doc-review-guidelines.md, and code-review-guidelines.md.

When do I need to generate a manual checkpoint in my development workflow?

You need a manual checkpoint after extended development work to capture the status quo, compute a diff against the last state, and produce structured documentation and code-review guidelines.

Can I use this checkpoint process if I don't have a previous checkpoint to diff against?

Yes, the checkpoint process determines the previous checkpoint automatically; if none exists, it establishes the initial baseline state and generates the status-quo summary and review guidelines.

What is the best way to automate code review checkpoints after extended development?

The best way to automate code review checkpoints is using the Make Checkpoint skill, which computes a YYMMDD timestamp, organizes repository state, and outputs tailored documentation and code review guidelines.