← ClaudeAtlas

cf-checkpoint-fromlisted

Load a saved checkpoint as working context, then do the next ask. Triggers: "resume from checkpoint", "load checkpoint", "continue from checkpoint", "cf-checkpoint-from", "restore conversation context". First word is the slug; `--recap` prints a summary. Does NOT create checkpoints (use $cf-checkpoint).
dinhanhthi/coding-friend · ★ 3 · AI & Automation · score 79
Install: claude install-skill dinhanhthi/coding-friend
# $cf-checkpoint-from 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 ```! bash "${PLUGIN_ROOT}/lib/load-custom-guide.sh" cf-checkpoint-from ``` If the block above printed anything, apply only the `## Before`, `## Rules`, and `## After` sections; if it shows the raw command instead of output, re-run that exact `load-custom-guide.sh` fence now. ### Step 1: Parse the argument Split `$ARGUMENTS` into three parts: 1. **`--recap` flag** — remove it from anywhere in the argument first. Its presence s