Skip to content
Agentmart
Submit a tool

checkpoint-semantics

Git-backed checkpoints and rollback composition — naming, nesting, conflicts, when to auto-commit.

Skill by xanstomper

IndexedMIT★ 1
Write a review

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/xanstomper-checkpoint-semantics

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

Git-backed checkpoints and rollback composition — naming, nesting, conflicts, when to auto-commit. Use when touching src/repo/ or checkpoint/rollback flows.

Reviews

Write a review

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-semantics

What's inside

Skill name
checkpoint-semantics
Description
Git-backed checkpoints and rollback composition — naming, nesting, conflicts, when to auto-commit. Use when touching src/repo/ or checkpoint/rollback flows.
License
MIT
Instructions
25 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Checkpoint Semantics

Checkpoints are git-backed named snapshots; rollback restores them. Composition rules keep them trustworthy.

## Trigger
- Touching `src/repo/`, checkpoint, rollback, or auto-commit flows.
- Designing a new mutating agent action.

## Steps
1. Every mutating agent action gets an automatic checkpoint BEFORE the mutation (`mochi fix` does this — follow the pattern).
2. Checkpoint names: human-readable intent (`mochi fix`, `mochi commit <msg>`), not timestamps — users read them in `mochi rollback` listings.
3. Rollback is itself checkpointed: a rollback creates a checkpoint of the current state first, so rollback is never destructive-irreversible.
4. Conflicts: if the working tree has changes when restoring, block and tell the user to checkpoint or stash first — never merge silently.
5. Untracked files are included in checkpoints; ignored files are not. Verify with a test that creates both.

## Pitfalls
- Empty commits on no-op checkpoints pollute listings — detect no-op and mark it.
- Nested repos (submodules, vendored clones): operate on the detected project root only.
- `git` absence or corrupt index must degrade to a clear error, never a partial restore.

## Verification
- `npx vitest run src/repo/` green.
- Manual: mutate → rollback → verify tree byte-identical to pre-mutation (checksum), rollback the rollback → original restored.

From xanstomper/mochi, MIT.

More from xanstomper/mochi

Signals

Stars
1
Forks
2
Open issues
6
Last commit (this folder)
Oct 12, 2026 (16 days ago)
Last release
Oct 23, 2026 (5 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
Repository
github.com/xanstomper/mochi
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from xanstomper

Cite this page

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