---
name: rcode-checkpoint-preview
internal: true
description: "LLM-assisted human-in-the-loop review."
triggers:
  - "checkpoint preview"
  - "preview the checkpoint"
  - "human-in-the-loop review"
  - "review before checkpoint"
  - "checkpoint review session"
  - "preview changes before approval"
user-invocable: true
---

## Overview

Checkpoint preview skill for rcode.

## Do NOT use this skill for

- **Automated code review without a human** — use `/rcode-review --karpathy` or a code-reviewer agent directly.
- **Approving a deploy or merge** — this skill explains a change; it does not authorize git push, deploys, or PR merges.
- **Bug investigation** from scratch — use `/rcode-debug` or the diagnose-issues workflow.
- **Architecture review of an undelivered design** — this skill reviews delivered code/diffs, not specs.
- **Sprint retros or milestone closure** — use `rcode-retrospective` or `rcode-complete-milestone`.

If the user has not produced a diff or change to review, ask them to do so first instead of invoking this skill.

## Workflow


# Checkpoint Review Workflow

**Goal:** Guide a human through reviewing a change — from purpose and context into details.

You are assisting the user in reviewing a change.

## Global Step Rules (apply to every step)

- **Path:line format** — Every code reference must use CWD-relative `path:line` format (no leading `/`) so it is clickable in IDE-embedded terminals (e.g., `src/auth/middleware.ts:42`).
- **Front-load then shut up** — Present the entire output for the current step in a single coherent message. Do not ask questions mid-step, do not drip-feed, do not pause between sections.
- **Language** — Speak in `{communication_language}`. Write any file output in `{document_output_language}`.

## INITIALIZATION

Load and read full config from `{project-root}/.rcode/config.yaml` and resolve:

- `implementation_artifacts`
- `planning_artifacts`
- `communication_language`
- `document_output_language`

## FIRST STEP

Read fully and follow `./step-01-orientation.md` to begin.

## Output Format

- 5-step walkthrough output inline in conversation (orientation → walkthrough → detail → testing → wrapup)
- Each step front-loaded (entire step in one message, no drip-feed, no mid-step questions)
- All code references use CWD-relative `path:line` format
- Trail artifact generated per `./generate-trail.md` at end

## Examples

### Happy Path
**Input:** `/rcode-checkpoint-preview` after a feature branch is complete
**Expected:** 5-step human review session with clear focus on what matters, testing recommendations, wrapup decision.

### Edge Case: No changes to review
**Expected:** Exit early, suggest the user make changes first.

## When NOT to use this skill

Do NOT use this skill for autonomous execution without a human (it is human-in-the-loop by design), for full code review (use rcode-review), or for phase verification (use rcode-verify-phase).
