cf-checkpoint-from

/cf-checkpoint-from

CLI Requirement: NONE — Works without coding-friend-cli. Reads the checkpoint file directly from disk; no CLI features are required. See CLI requirements for the full matrix.

Argument: $ARGUMENTS

Purpose

Load a saved checkpoint into the current (fresh) conversation as working context — goal, state, decisions, next steps — then continue the task. This is the counterpart to /cf-checkpoint, which captures that context; this skill only reads and restores it, it never creates or edits a checkpoint file.

IMPORTANT — path resolution:

• Use MAIN_REPO_ROOT from the SessionStart bootstrap context (injected via session-init.sh). If absent, fall back to running pwd for $CWD and use $CWD as MAIN_REPO_ROOT.
• Read config from CF_CONFIG_FILE (= $MAIN_REPO_ROOT/.coding-friend/config.json) — do NOT search sub-folders.
• Use CF_DOCS_ROOT as the docs base dir (= $MAIN_REPO_ROOT/{docsDir} where docsDir comes from config, default docs).
• Checkpoints live under {CF_DOCS_ROOT}/context/checkpoints/.
• Always resolve paths as absolute paths — never relative, they may resolve incorrectly when the working directory contains nested git repos.

Workflow

Step 0: Custom Guide

Custom guide — auto-loaded below (if the raw command shows instead of its output, run it yourself):

bash "<plugin-root>/lib/load-custom-guide.sh" cf-checkpoint-from

If output is not empty, integrate returned sections: ## Before → before first step, ## Rules → apply throughout, ## After → after final step.

Step 1: Parse the argument

Split $ARGUMENTS into three parts:

1. --recap flag — remove it from anywhere in the argument first. Its presence sets recap ON (default OFF). It is not part of the slug or the message.
2. Checkpoint slug — the first remaining token (a bare <slug> or a full file path).
3. User message — everything after that first token. This is the trusted instruction: what to do once context is loaded. May be empty.