rianprei

Snapedit — AI skill for Claude Code

AI community

Snapshot-based editing for AI agents: send only the NEW content via stdio MCP.

How to install Snapedit

This entry records only its repository, not the path inside it, so there is no exact command to give. Open rianprei/snapedit and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Snapedit does

Snapshot-based editing for AI agents: send only the NEW content via stdio MCP. Immutable sha256 snapshots, 3-way merge, conflict detection, ambiguity-safe zero-write applies, cross-process locks.

Alternatives in AI

MuseAI Skills — muse.ai (Muse AI) skills and runtime snapshot: 68 skills, workflow guides, connector manifests 261 ★
Imprint Memory — Persistent memory system for Claude Code — hybrid search (FTS5 + vector), message bus, task queue 78 ★
RelayBrain — Coordination and context layer for AI coding agents 31 ★

README

snapedit

Snapshot-based file editing for AI agents — **send only the NEW content, never the old block.**

[![Node.js](https://img.shields.io/badge/node-%3E%3D18-339933)](https://nodejs.org/) [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE) [![MCP](https://img.shields.io/badge/protocol-MCP-%23f59e0b)](docs/PROTOCOL.md) [![Tests](https://img.shields.io/badge/tests-55%2F55%20passing-brightgreen)](test/snapedit.test.js)

`snapedit` lets an editing agent (Claude Code, OpenCode, or any MCP client) edit files by sending **only the new content** — never the old text. Files are captured as immutable, content-addressed snapshots; edits reference the snapshot's 1-based line numbers, so lines shifted by prior edits elsewhere never silently misapply.

Agent                            snapedit                     Filesystem
  │  read_snapshot(path)            │
  ├────────────────────────────────►│  sha256(bytes) → blob_id
  │◄── blob_id + numbered page ────┤
  │                                 │   …(agent thinks)…
  │  apply_snapshot_patch(blob,     │
  │    from, to, NEW_CONTENT) ──────►│  base=snapshot · ours=live
  │                                 │  3-way merge OR splice
  │◄── ok:true / conflict / err ────┤
  │                                 │  atomic write + lock

Why

Direct rewrite tools force the agent to transmit the old text to locate a change; when a file changes between reads, misalignment silently corrupts files. `snapedit` replaces that with:

Immutable snapshots — blob_id = sha256(bytes). The agent carries only the id; content is never re-sent.
3-way merge on apply — base = snapshot, ours = live file. Earlier edits (even insertions above the hunk) are preserved; the patch lands exactly where the snapshot said it should.
Explicit conflicts — if the live file changed inside the hunk with different content, no write happens; a structured conflict is returned with previews of both sides.