Skip to content
Agentmart
Submit a tool

checkpoint-save

Use when pausing work that will be resumed later, when switching contexts, or when the user asks to save a checkpoint.

Skill by laurac8r

IndexedMIT★ 3
Write a review

Chalk Labs

Need help deploying checkpoint-save?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/laurac8r-checkpoint-save

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use when pausing work that will be resumed later, when switching contexts, or when the user asks to save a checkpoint. Creates a CHECKPOINT.md that captures full resumption context.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/checkpoint-save

Tools it pre-approves 27

From allowed-tools in SKILL.md: the agent may use these without asking you each time.

  • Bash(git
  • branch
  • --show-current),
  • rev-parse
  • --show-toplevel),
  • --path-format=absolute
  • --git-common-dir),
  • status:*),
  • diff:*),
  • log:*),
  • add
  • CHECKPOINT.md),
Show 15 more
  • Bash(basename:*),
  • Bash(dirname:*),
  • Bash(mkdir:*),
  • Bash(cp
  • CHECKPOINT.md
  • .checkpoints/*.mirror.md),
  • Bash(mv
  • .checkpoints/*.md),
  • Bash(stat:*),
  • Bash(date:*),
  • Read,
  • Write(CHECKPOINT.md),
  • Write(.checkpoints/*.md),
  • Edit(CHECKPOINT.md),
  • Edit(.checkpoints/*.md)

What's inside

Skill name
checkpoint-save
Description
Use when pausing work that will be resumed later, when switching contexts, or when the user asks to save a checkpoint. Creates a CHECKPOINT.md that captures full resumption context.
License
MIT
Allowed tools
Bash(git, branch, --show-current),, Bash(git, rev-parse, --show-toplevel),, Bash(git, rev-parse, --path-format=absolute, --git-common-dir),, Bash(git, status:*),, Bash(git, diff:*),, Bash(git, log:*),, Bash(git, add, CHECKPOINT.md),, Bash(basename:*),, Bash(dirname:*),, Bash(mkdir:*),, Bash(cp, CHECKPOINT.md, .checkpoints/*.mirror.md),, Bash(mv, CHECKPOINT.md, .checkpoints/*.md),, Bash(stat:*),, Bash(date:*),, Read,, Write(CHECKPOINT.md),, Write(.checkpoints/*.md),, Edit(CHECKPOINT.md),, Edit(.checkpoints/*.md)
Instructions
427 lines in SKILL.md · view on GitHub

Before installing

  • Pre-approves some shell commands

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Checkpoint Save

Pause here and create a checkpoint CHECKPOINT.md file to allow us to quickly
resume work on this later. Use / reference memories as needed.

## What to Capture

Create `CHECKPOINT.md` in the project root (or working directory) with:

```markdown
# Checkpoint: [Brief Title]

**Date:** [today's date] **Branch:** `[current git branch]` **Session context:**
[1-2 sentence summary of what we were doing]

## Current State

- What's been completed
- What's in progress (with file paths and line numbers)
- What's not yet started

## Next Steps

1. [Exact next action to take]
2. [Following actions in order]

## Key Decisions Made

-

[Decision]: [Why] (so we don't re-debate)

## Open Questions / Blockers

- [Anything unresolved]

## Files Modified

- [List of files changed in this session, with brief note on what changed]

## Relevant Memories

- [Reference any memory files that provide context for this work]

## Resume Command

[Exact prompt or slash command to resume, e.g. "Continue from CHECKPOINT.md"]
```

## Process

### Step 1 — Compute current-branch slug

Run `git branch --show-current` to get the current branch name. If the output is
empty (detached HEAD), fall back to the basename of CWD (`basename "$PWD"`).
Apply slug rules to produce `<slug>`:

1. Lowercase.
2. Replace `/` with `-`.
3. Strip characters outside `[a-z0-9-]`.
4. Collapse consecutive `-`.

### Step 2 — Resolve archive directory

Run:

```
COMMON_DIR=$(git rev-parse --path-format=absolute --git-common-dir)
```

If this command exits non-zero, abort: **"Not a git repository. checkpoint-save
requires a git repo at CWD."**

Then:

```
ARCHIVE=$(dirname "$COMMON_DIR")/.checkpoints
mkdir -p "$ARCHIVE"
```

This resolves to the **main checkout root's** `.checkpoints/` directory,
ensuring all git worktrees share a single archive.

### Step 3 — Verify `.gitignore` coverage

Check whether `.checkpoints/` is listed in the main checkout's `.gitignore` (the
`.gitignore` at `$(dirname "$COMMON_DIR")/.gitignore`). If the line is absent,
append `.checkpoints/` to that `.gitignore` and report to the user:

> "Added `.checkpoints/` to `.gitignore` in the main checkout. Please review and
> commit that change when ready."

Do NOT auto-commit — the user handles all git commits.

### Step 4 — Handle existing CHECKPOINT.md

If `CHECKPOINT.md` exists at CWD, parse its `**Branch:**` line and apply one of
the four cases below. **Before auto-selecting Case A (same branch), also check
for the Case D escape hatch** — a same-branch CHECKPOINT.md may belong to an
unrelated live effort, not a stale version of current work.

**Case A — Same branch as current, same effort (stale version of current
work):** Copy the existing file to `.checkpoints/<slug>.prev.md` (overwrite any
prior `.prev.md`). This is a rolling single-slot backup before the same-branch
overwrite. Use this when the existing checkpoint's **Current State** section
describes the same work you're about to re-checkpoint — it's a natural
supersession.

**Case B — Different branch:** The existing checkpoint belongs to a different
effort. Derive `<old-slug>` from the `**Branch:**` value in the existing file
(apply the same slug rules). Move (not copy) the existing `CHECKPOINT.md` to
`.checkpoints/<old-slug>.md`. On collision (file already exists), append `-2`,
`-3`, etc. until the name is free.

**Before proceeding to Step 5, verify the `mv` succeeded.** If it fails
(permissions, disk full, cross-device), abort: **"Failed to archive existing
CHECKPOINT.md. The old checkpoint is still at CWD. Resolve the mv failure before
retrying."** Do not overwrite `CHECKPOINT.md` until the archive is confirmed.

From laurac8r/claude-damn, MIT.

More from laurac8r/claude-damn

Signals

Stars
3
Forks
1
Open issues
0
Last commit (this folder)
Jul 7, 2026 (4 months ago)
Last release
Jul 19, 2026 (3 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from laurac8r

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get checkpoint-save running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying checkpoint-save?

CallGet help
Cite this page

checkpoint-save skill. Agent Mart. https://agentmart.dev/skills/laurac8r-checkpoint-save (last updated 2026-10-24)