bm-checkpoint

Writes structured work checkpoint notes to Basic Memory with git, PR, and verification context.

4.0k|282|Updated Dec 2, 2024
One-click install
npx skills add https://github.com/basicmachines-co/basic-memory --skill bm-checkpoint-basicmachines-co
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bm-checkpoint
Source: https://github.com/basicmachines-co/basic-memory/tree/main/plugins/claude-code/skills/bm-checkpoint
Command: npx skills add https://github.com/basicmachines-co/basic-memory --skill bm-checkpoint-basicmachines-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Work context is lost when a coding session ends, a conversation is compacted, or a task is handed off. This Skill captures the full state of the work—story, changed files, verification results, decisions, blockers, and next action—as a durable Markdown note in Basic Memory that any human or agent can resume from later. ## Core Features & Use Cases - Deliberate checkpoint capture: Gathers evidence including git status, branch, SHA, pull request details, changed files, tests run, decisions, and blockers before writing the note. - Profile-aware note schemas: Supports a general session profile and a coding profile with required frontmatter fields like repository, repo_root, branch, and git_sha, plus typed pull request metadata. - Structured recall: Uses typed observations ([result], [decision], [blocker], [next_step]) and Basic Memory relations so checkpoints compound into a searchable knowledge graph. - Use Case: Before ending a long debugging session, ask for a checkpoint; the Skill writes a note titled "Claude checkpoint - <topic>" with the story, verification results, and the exact next action, then replies with the permalink. ## Quick Start Ask the assistant to checkpoint the current work to Basic Memory, optionally giving a short topic for the note title.

Frequently Asked Questions about bm-checkpoint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save a work checkpoint in Basic Memory from Claude Code?▼

Ask the assistant to checkpoint, wrap up, or hand off the current work, optionally with a short topic. The Skill gathers git state, changed files, and verification results, then writes a structured note to your configured Basic Memory project and returns its permalink.

What information does a Basic Memory checkpoint note include?▼

A checkpoint includes a summary, the story of the work, changed files, verification results, and typed observations for decisions, blockers, and next actions. Coding sessions also record repository, branch, git SHA, and pull request metadata in the frontmatter.

Does the checkpoint skill require any configuration?▼

It reads the basicMemory block from Claude settings files, using primaryProject, captureFolder, and sessionProfile keys with documented defaults. The coding profile additionally requires a repository identifier, and the Skill stops if required coding fields cannot be proven.

How does the checkpoint skill handle pull request metadata?▼

When the current branch has a pull request, it runs a read-only GitHub query such as gh pr view to capture the PR number, title, URL, state, base, and head as typed frontmatter fields. These fields are omitted when no PR exists and are never inferred from conversation text.

When should I use a deliberate checkpoint instead of automatic capture?▼

Use a deliberate checkpoint before long context transitions, handoffs, or when wrapping up meaningful work, since it produces a high-signal narrative note. Automatic PreCompact checkpoints handle routine session continuity without the curated story and verification detail.