Bm Checkpoint
Create an immutable Codex handoff in Basic Memory and return an exact bm-orient resume...
Install
npx skills add basicmachines-co/basic-memory --skill bm-checkpoint -g -a claude-code -y- Repository
- basicmachines-co/basic-memory4.4k
- Category
- Engineering
- Updated
- 3d ago
- License
- AGPL-3.0
- Context cost
- Mediumabout 2,548 tokens
- Runs scripts
- No, instructions only
What it does
Create an immutable Codex handoff in Basic Memory and return an exact bm-orient resume command.
Checkpoint Codex Work
Create a durable, immutable handoff note for current Codex work. Use this when the user asks to checkpoint, wrap up, hand off, remember the work state, or when the post-compaction SessionStart context requests the deliberate handoff.
When no project is pinned, discover projects with bm_project(command="list")
and pass the selected project's external ID as project on note/search calls.
With several addressable projects, these calls require an explicit scope even
when a default is configured.
Gather
Read ~/.codex/basic-memory.json, then the nearest project
.codex/basic-memory.json; project keys override user keys:
primaryProject, default omittedcaptureFolder, defaultcodex/<git top-level directory name>placementConventions, optionalsessionProfile, defaultgeneralrepository, required whensessionProfileiscoding
Apply the bm-writing skill before drafting the note.
Gather repo evidence:
- the original objective that started the thread and why it mattered
- the latest user intent, including corrections or scope changes that supersede the original objective
- the approach taken and why it solves the problem
- the current system state and practical impact
- tradeoffs, sharp edges, useful simplifications, and intentionally parked work
git status --short- current branch
- repository root and current working directory
- current Git SHA
- current pull request number, title, URL, state, base, and head when one exists
- changed files you touched
- tests or checks actually run
- failures or skipped checks
- decisions made in this thread
- unresolved blockers
- next action
- current username, hostname, and timestamp
- host-provided
session_id,agent,codex_turn_id,trigger, andmodelvalues from the checkpoint request, when present
