Skills

Checkpoint

Save a structured state snapshot before stopping or handing off.

Install

npx skills add pedrohcgs/claude-code-my-workflow --skill checkpoint -g -a claude-code -y
Category
Engineering
Updated
1mo ago
License
MIT
Context cost
Mediumabout 2,639 tokens
Runs scripts
No, instructions only

What it does

Save a structured state snapshot before stopping or handing off. Captures the active plan, recent decisions, file pointers (with line numbers), open questions, and the next 1, 3 actions into a checkpoint file under `quality_reports/checkpoints/`. Optionally proposes `[LEARN]` entries to add to MEMORY.md. Use when user says "checkpoint", "save state", "snapshot before I stop", "where am I", "wrap up the session for handoff", or before a long break / model switch / collaborator handoff. Companion to (NOT replacement for) the narrative session-log workflow.

<!-- Pattern adapted from Hugo Sant'Anna's clo-author v4.2.0 (github.com/hugosantanna/clo-author), used with permission. Original /checkpoint shape: project-level session handoff with state snapshot + memory updates. This implementation is reimplemented in original prose against this template's narrative-session-log + plan-on-disk + auto-memory architecture. Attribution credit: Hugo Sant'Anna. -->

/checkpoint, Structured Session Handoff

Produce a state snapshot that the next session (yours, or a collaborator's, or a fresh-context reboot) can resume from in under a minute. The narrative quality_reports/session_logs/ continues to live separately, /checkpoint writes the structured side: facts, file pointers, and next-actions.

When to use

  • Before a long break, model switch (Opus ↔ Sonnet ↔ Haiku), or end of a working day.
  • Before auto-compaction would otherwise discard mid-plan context (paired with the PreCompact hook).
  • Before handing off to a collaborator on the same repo.
  • After completing a chunk of a multi-session plan, when "where am I" is the first question the next session will ask.

When NOT to use

  • For the narrative what happened, that lives in quality_reports/session_logs/ (see .claude/rules/session-logging.md).
  • For commit messages, those go through /commit, which writes its own structured commit body.
  • For decisions about alternatives, those go to templates/decision-record.md via quality_reports/decisions/.

The three artifact types are complementary: session-log = narrative, decision-record = trade-off captured, checkpoint = state to resume from.

Workflow

PHASE 1, Gather state

Read, in this order:

Read the whole SKILL.md on GitHub

More in Engineering