save git:20261019.54d61beA

Immutable. This exact content never changes and is served at /api/v1/blob/fa9a5437fa74eea4.

---
name: save
description: Checkpoint work: commit, push, update the PR, wait for CI, return the preview, record session facts. Never implements or merges.
user-invocable: true
---

# /save

`/save` authorizes branch creation, record upkeep, spec reconciliation, commit, push, PR updates and CI fixes; [ask](../explore/references/asking-the-user.md) for anything else. Never force push, bypass hooks, amend merged commits or merge: `/ship` owns archive/merge, and [the gate](../../../wiki/development/the-change-loop.md#the-gate) is never a local check.

`/save [note]`: a [Status value](../../../wiki/development/the-change-loop.md#the-change-is-a-living-handoff-not-just-a-plan) sets Status; other notes seed the Decision log. Cold-resume context belongs in pushed files with repo-relative paths: another computer reads it.

## 1. Protect credentials and select the route

**Keep every credential supplied, rotated, read or written this session out of** tracked files, changes, facts, messages, PR text and reports. Values stay in working memory and their intended ignored live file; record only names and sources.

Load each matching procedure before its actions; conditions combine:

| Condition | Procedure |
|---|---|
| User supplied or rotated an explicitly named secret | [Named-secret persistence](references/named-secrets.md), before writing records |
| Confirmed routine/goal registration or lifecycle checkpoint | [Record-only delivery](references/schedule-records.md), before code selection |
| Only facts, including a to-do that changed no repo file | [Facts-only save](references/facts-save.md) |
| Code or a code plan needs a new change | [New-plan fallback](references/new-plan.md) |
| The exact selected handoff is archived | [The archived handoff](#the-archived-handoff) |

Check [preconditions](references/preconditions.md), then fetch `main` before comparing; errors stop.

```bash
git fetch origin main
openspec context --json
openspec list --json
bash "$(git rev-parse --show-toplevel)/.claude/skills/save/scripts/change-candidates.sh" --json
```

Save the change this work touched, found by [the rungs](references/checkpoint-evidence.md#selection-rungs), never a plan merely because it is the only one open. Keep `BRANCH`, `NAME`, `CHANGE_ROOT` separate: a branch and its change can differ in name, so never rename or duplicate a change to match.

A save changing repo files takes the normal route, except the validated record-only procedure above. Nothing learned, decided, or changed → report and stop.

## 2. Maintain the handoff and capture context

Keep the feature branch. On default/detached HEAD, `git checkout -b "$SLUG"`: change/topic name, else worktree name for an unreadable session; append a short SHA on collision. Create required plan artifacts before checkpointing.

Maintain the living handoff:

- Proposal header: current `**Status:**`, actual `**Branch:**`, and `**Open questions:**` (`none` when empty).
- Plan sections: the current intent from the latest agreed plan and diff, self-contained, edited in place under existing headings. Tasks: true checked state and agreed additions.
- `## Decision log`: append one dated entry; never change earlier ones: a cold reader inherits the why from them.
- Session facts: [write them](../memory/references/writing-facts.md) through [the memory write gate](../memory/SKILL.md#write) with `"session": "current"` and `"source": "save"`. A spooled result does not block the save.

For an active change, [reconcile its deltas](../plan/references/openspec-cli.md#reconcile-deltas). Read artifact and task progress [from the CLI](../plan/references/openspec-cli.md#create-or-read-a-change).

### The archived handoff

Keep exact `CHANGE_ROOT`; infer `NAME` from its dated folder only if absent. Retain actual Branch and append a dated archive-checkpoint entry. The archive is the record: never rebuild the plan or recreate an active folder; archive already reconciled deltas. Stage archive, tracked removals and implementation; pass `--mode archive` and report its path.

## 3. Stage, exclude values, and commit

Stage intended implementation, handoff and removals, never `git add .`, which sweeps in unmeant files; check for unrelated staged work. A plan-only save commits its artifacts. Write, outside the repo, a one-line repo-style commit message ending `Co-Authored-By: Claude`, and the PR summary.

## 4. Publish and wait for the gate

One command runs [the gate](references/git-gate.md), review page to preview:

```bash
node "$(git rev-parse --show-toplevel)/.claude/skills/save/scripts/checkpoint.mjs" \
  --message-file "$MESSAGE" --summary-file "$SUMMARY" \
  --change-root "$CHANGE_ROOT" --mode active --scan-keys "$KEYS"
```

`--scan-keys` names every credential handled this session; a match stops the save. No change → omit `--change-root` and `--mode`. Use the host's longest wait and wait again, silently, until it ends; then follow its `NEXT:` line.

## 5. Report

Report outcome and one link in plain words. Inside a verb or on request, include branch/commit, PR, change/archive Status, fact counts and stored/spooled/skipped state, CI fixes/uncertainty and preview/absence. Return the command's `SAVE_HEAD`, [`RECEIPT`](references/git-gate.md#saved-revision-handoff) and `SAVE_GATE_RESULT` lines; always print the last inside a verb. Explicit errors; continue command only for active changes.

Direct invocation asks [next steps](../explore/references/asking-the-user.md#end-every-reply-with-the-next-step) with the question tool: continue, publish or stop; failed/unverified gates offer repairs.