Checkpoint preview — e11-checkpoint-preview

LLM-assisted human-in-the-loop review. Where e11-code-review puts subagents to work finding problems, checkpoint preview puts you in front of the change and makes sense of it with you — orientation first, detail only where it matters.

When to use it

• A change is in-review (from e11-dev-flow, e11-dev-auto, or a story) and you want to actually understand it before approving.
• A PR from anywhere — the skill works on any diff, PR, or story in review.
• After an unattended run flagged followup_review_recommended.
• Not a substitute for [CR] — checkpoint informs you; code review produces triaged findings.

How to invoke

[CP] from the Phase 4 catalog, or invoke e11-checkpoint-preview and point it at a diff, branch, PR, or spec/story. Say "checkpoint", "human review", or "walk me through this change" and it triggers.

The walkthrough

Five steps, human-paced:

1. Orientation — what this change is for, what it touches, how big the blast radius is. You say what you care about.
2. Concern-based walkthrough — the change grouped by the concerns you named (plus ones it thinks you should have), not by file order.
3. Risk-focused detail pass — the diff hunks that deserve close reading, with the reasoning about why.
4. Hands-on testing — concrete suggestions for poking the change yourself (commands, URLs, edge inputs).
5. Wrap-up + trail — a trail file records what was reviewed, what you looked at closely, and what you decided, so the checkpoint is auditable later.

Gotchas

• It doesn't gate anything by itself. The output is your informed judgment plus the trail — pair it with the sprint board or your PR flow for enforcement.
• Scope the diff first. Pointing it at a week of commits produces a week-sized walkthrough. Give it the story or branch you mean.

Customization

.foundry/custom/e11-checkpoint-preview.toml — persistent_facts (e.g. "we always check authorization changes by hand"), activation steps, on_complete. See Customization.

Source

e11-checkpoint-preview/SKILL.md

See also: Phase 4 · Unattended runs · Run an adversarial review.