dev-resumelisted

Resume work from a previous session checkpoint. Uses `resume-context` CLI to load feature, checkpoint, git state, and session history in a single call, then synthesizes a focused resumption summary before continuing. Use at the start of a new session to restore context from a previous checkpoint.
andreaserradev-gbj/dev-workflow · ★ 2 · AI & Automation · score 76

Install: claude install-skill andreaserradev-gbj/dev-workflow

## Resume From Checkpoint ### Step 0: Discover Project Root Run the [discovery script](scripts/discover.sh): ```bash bash "$DISCOVER" root ``` Where `$DISCOVER` is the absolute path to `scripts/discover.sh` within this skill's directory. **Path safety** — shell state does not persist between tool calls, so you must provide full script paths on each call: - **Use `$HOME`** instead of the literal home directory (e.g., `bash "$HOME/code/…/discover.sh"`, not `bash "/Users/name/…/discover.sh"`). This prevents username hallucination. - **Copy values from tool output.** When reusing a value returned by a previous command (like `$PROJECT_ROOT`), copy it verbatim from that command's output. Never retype a path from memory. - **Verify on first call**: if a script call fails with "No such file", the path is wrong — STOP and re-derive from the skill-loading context. - **Never ignore a non-zero exit.** If any script in this skill fails, stop and report the error before continuing. Store the output as `$PROJECT_ROOT`. If the command fails, inform the user and stop. ### Step 1: Identify Feature to Resume Run the [discovery script](scripts/discover.sh) to find checkpoints: ```bash bash "$DISCOVER" checkpoints "$PROJECT_ROOT" "$ARGUMENTS" ``` Pass `$ARGUMENTS` as the third argument only if the user provided one; omit it otherwise. - If the script exits non-zero (no `.dev/` directory): inform the user, stop. - If output is empty: no checkpoints found, ask what to work on. - If one l