aped-checkpoint

Summarize recent git diffs and pipeline state for human approval.

2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/yabafre/aped-claude --skill aped-checkpoint
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aped-checkpoint
Source: https://github.com/yabafre/aped-claude/tree/main/src/templates/skills/aped-checkpoint
Command: npx skills add https://github.com/yabafre/aped-claude --skill aped-checkpoint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

APED checkpoint helps you confidently review what the model changed by pausing mid-pipeline and summarizing recent diffs so you can approve, request fixes, or abort.

Core Features & Use Cases

  • Human-in-the-loop change review: Produces a concern-ordered summary (risks, assumptions, deviations, then info) and stops for explicit user confirmation.
  • Diff- and state-aware auditing: Uses git diff and, when present, reads {{OUTPUT_DIR}}/state.yaml to ground the summary in the pipeline’s current phase/story.
  • Drift trigger guardrails: Scans recent assistant turns for re-anchor triggers to prevent drifting summaries after spec or location mistakes.
  • Safety against unintended progression: Acts as a read-only checkpoint that does not modify state.yaml or advance the pipeline.

Quick Start

Tell the assistant: checkpoint and review the changes since the last checkpoint, then stop and wait for your approval.

Frequently Asked Questions about aped-checkpoint

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

FAQPage Schema
How do I pause an automated pipeline for a human-in-the-loop code review?▼

Human-in-the-loop code review pauses automated pipelines by summarizing recent git diffs and pipeline state, halting progression until explicit user approval is granted. The checkpoint acts as a read-only gate requiring manual confirmation before proceeding.

How does a git diff summary help verify pipeline state before proceeding?▼

A git diff summary verifies pipeline state by analyzing recent code and artifact changes alongside a state.yaml file. It generates a concern-ordered summary highlighting risks, assumptions, and deviations to ground the review in the pipeline's current phase.

What is the best way to prevent pipeline drift after spec or location mistakes?▼

Preventing pipeline drift uses drift trigger guardrails that scan recent assistant turns for re-anchor triggers. This catches spec or location mistakes early, ensuring the checkpoint summary remains accurate and preventing unintended state progression.

Can I use a read-only checkpoint to audit code changes without modifying state.yaml?▼

Yes, a read-only checkpoint audits code changes without modifying state.yaml or advancing the pipeline. It requires running a check-enabled.sh script for activation gating and generates a concern-ordered summary without making any state changes.

Do I need a state.yaml file to generate a concern-ordered diff summary?▼

A state.yaml file is optional for generating a diff summary. The checkpoint uses git diff as the primary source and reads state.yaml when present to add pipeline context, grounding the summary in the current phase or story.