mcpField
C
checkpoint-read

checkpoint-read

github.com/desekAgent workflows342 installsUpdated 1d ago
Repository

About checkpoint-read

checkpoint-read is an agent skill for recovering project context at the start of a session. It reads local Git checkpoint history and summarizes completed work, pending items, and recorded decisions without changing repository state.

Key features

  1. 01Lists recent checkpoint commits
  2. 02Reads the latest checkpoint details
  3. 03Summarizes completed and pending work
  4. 04Reports recorded decisions and reference data
  5. 05Uses read-only local Git queries

Use cases

  1. 01Recovering context at the start of a session
  2. 02Reviewing work and TODOs from a checkpoint
  3. 03Finding decisions recorded in Git history

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/desek/governance --skill checkpoint-read

After installing, type/checkpoint-readin Claude Code to confirm it loaded.

Bundled filesCHANGELOG.mdversion.txt

Details

From the project README

/checkpoint-read

Reads checkpoint commit history to recover project context when starting a new session. Queries Git history for checkpoint commits created by /checkpoint-commit, displays the most recent relevant checkpoint details, and summarizes what was implemented, what remains, and any decisions captured — enabling seamless session continuity.

Usage: /checkpoint-read

No arguments required. The command automatically reads the most recent checkpoint commits from local Git history.

Workflow

Follow these steps in order.

Step 1: List Recent Checkpoints

Query Git history for checkpoint commits:

git log --oneline --decorate --grep '^checkpoint.*:' -n 25
  • If no results: Report "No checkpoint commits found in this repository." and STOP. Proceed with the session without checkpoint context.
  • If results exist: Display the list of recent checkpoint commits to provide an overview of checkpoint history.
Step 2: Read Most Recent Checkpoint

Extract the SHA from the most recent (first) checkpoint in the list, then read its full details:

# Show commit stats (files changed)
git show --stat {SHA}

# Show full commit message and diff
git show {SHA}

Parse the commit message subject line and body for context recovery.

Step 3: Summarize Context

Analyze the checkpoint commit message and produce a structured summary with three sections:

  1. What was implemented: Extract completed work from the commit body bullet points and diff content.
  2. What remains: Identify pending items, TODOs, or incomplete work mentioned in the commit message.
  3. Decisions captured: Note any architectural or design decisions recorded in the commit message.
Step 4: Report

Present the structured summary to the user, including:

  • The checkpoint commit SHA and date for reference
  • The CR identifier from the commit subject (e.g., CR-XXXX)
  • The three-section context summary (implemented, remaining, decisions)

Safety Rules

  • MUST NOT perform destructive Git operations: git reset, git rebase, git commit --amend, git push --force
  • MUST NOT create commits, modify files, or alter Git state in any way
  • MUST be entirely read-only — only Git query commands are permitted
  • MUST rely only on local Git operations (no network calls)

Comments

Markdown supported