cf-checkpoint-from

Solid

Load a previously saved checkpoint file back into a fresh conversation as working context, then do what the user asks next. Use when the user wants to resume from a saved checkpoint — e.g. "resume from checkpoint", "load checkpoint", "continue from checkpoint", "cf-checkpoint-from", "pick up from the saved context", "restore conversation context". First word of the argument is the checkpoint slug; anything after it is what to do once context is loaded. Pass `--recap` to also print a summary of the restored context. Requires an existing checkpoint file — does NOT create checkpoints (use $cf-checkpoint for that).

Data & Documents 3 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 79/100

Stars 20%
20
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# $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](../../../docs/cli-requirements.md) 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 r...

Details

Author
dinhanhthi
Repository
dinhanhthi/coding-friend
Created
5 months ago
Last Updated
today
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

cf-checkpoint

Save a concise checkpoint of the current conversation's context — goal, decisions, breaking changes, next steps — into a file for resuming later in a DIFFERENT conversation. Use when the user says things like "save a checkpoint", "checkpoint this conversation", "capture context", "snapshot the conversation", "cf-checkpoint". Unlike /compact (condenses context within the SAME conversation), this produces a durable, resumable snapshot for a fresh conversation. Unlike $cf-remember (durable project-wide facts/conventions for AI recall across all future work), this is a transient per-conversation resume artifact. Does NOT auto-invoke — slash-only.

3 Updated today
dinhanhthi
AI & Automation Listed

loamcheckpointing

Use when pausing, shutting down, handing off, or context-switching active work and future sessions need a compact resumable checkpoint derived from the current session context. Writes a small checkpoint note under wiki/checkpoints/ and then optionally records the user's intended return step. Not for durable learnings capture, wiki correction, or source ingestion.

0 Updated today
scchearn
Data & Documents Solid

checkpoint

Write a committed, cross-machine handoff snapshot - active plan, decisions made, file pointers with line numbers, open questions, and the next 1-3 concrete actions - to `.claude/session-reports/`. Use when the user says "checkpoint", "save state", "snapshot before I stop", "where am I", "wrap up for handoff", or before a long break, a model switch, or handing the repo to a collaborator. Auto-memory is machine-local and `/rewind` is in-session undo; the checkpoint is the artifact that travels with the repo.

0 Updated today
groundnuty