cds-checkpoint

Capture session checkpoints from status files, git diffs, and decisions.

Updated Feb 2, 2026
One-click install
npx skills add https://github.com/xanderscannell/Claude-CDS-Prevention --skill cds-checkpoint
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cds-checkpoint
Source: https://github.com/xanderscannell/Claude-CDS-Prevention/tree/main/skills/cds-checkpoint
Command: npx skills add https://github.com/xanderscannell/Claude-CDS-Prevention --skill cds-checkpoint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Checkpoints capture a clear record of a session, linking plans, actions, and outcomes to improve continuity.

Core Features & Use Cases

  • Create a structured snapshot of what was planned, what was done, and what remains.
  • Update the current status and bootloader files to reflect progress and decisions.
  • Use ADR-like decisions to document architectural or process choices for future sessions.

Quick Start

In a project session, invoke the checkpoint to snapshot progress and commit the changes to the context directory.

Frequently Asked Questions about cds-checkpoint

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

FAQPage Schema
What is a session checkpoint and how does it preserve project progress?▼

To capture a session checkpoint, invoke the checkpoint command during a project session. It aggregates current status, recent git diffs, and decisions, writes the record to the checkpoints directory, updates status files, and suggests a commit to save changes.

How do I document architectural decisions during a development session?▼

Capturing a session checkpoint requires a project context directory containing current status and decisions files. It also aggregates recent git diffs, so a git repository with existing project documentation is needed to build a complete record.

What is the best way to save project context and status updates across sessions?▼

The best way to save project context is to capture a session checkpoint. It updates current status files and writes a timestamped record to a checkpoints directory, bridging the gap between plans, actions, and outcomes for future continuity.

How does capturing a checkpoint improve session continuity?▼

Capturing a checkpoint improves continuity by creating a structured snapshot of what was planned, what was done, and what remains. It updates current status files and logs architectural decisions so the next session resumes with full context.

Can I use a session checkpoint with my existing git workflow?▼

Yes, the checkpoint integrates with your git workflow by aggregating recent git diffs into the session record. After writing the checkpoint and updating status files, it suggests a git commit to save the context changes.