madeinplutofabio/vibe-revert

Protect the project you're actually working on.
Record · Check · Fix · Restore.
VibeRevert is the project-integrity layer for AI coding. It records the real working state before an agent starts, flags risky changes with deterministic rules, and lets you remove the agent work you don't want without giving up the rest.
**An agent changed 80 files. 75 are useful. Remove the 5 you don't.**
**No AI judges the AI:** risk findings are reproducible, explainable, and based on rules you can inspect.
**The working state you already had is part of the project.** Staged work, unstaged edits and pre-existing untracked files are recorded before the session starts and preserved through recovery. You don't have to package your work into commits before letting an agent help with it.
**Keep using your coding agent.** VibeRevert works alongside Claude Code, Cursor, and other coding-agent workflows. Git worktrees give an agent an isolated checkout; VibeRevert protects and selectively recovers the working state an agent actually changes. They solve different problems and can be used together.
*AI broke your project? Undo the session, not your week.* Whole-session rollback is still one command.
See it work
The actual CLI, condensed from a real beta payment run — check flags it, and rollback previews what it will change before you --apply:
Proof, not promises
**3 real AI coding sessions. 3 exact project-file restorations.** Payments, database migrations, and deployment infrastructure — all with pre-existing uncommitted work preserved. Read the beta report →
Quickstart
Works inside a Git repository and requires Node.js 22+. VibeRevert keeps its records on your machine and requires no VibeRevert account or hosted service.
Restoring only part of a session works the same way, with a selector:
What it protects you from
You let an AI agent work across your project, and it touched more than you expected — maybe payment code, a database migration, a deploy file — while your own half-finished work was sitting right there uncommitted. VibeRevert captures your project's starting file state first, so a session you don't like doesn't cost you your afternoon.
What VibeRevert does
Around each AI coding session, VibeRevert:
- **Checkpoints your project first** — working tree, staged changes, and untracked files, including work you haven't committed.
- **Records the session** and the project files that changed while it ran.
- **Flags risky edits** — changes touching auth, payments, databases, secrets, dependencies, or infrastructure (risk taxonomy).
- **Writes an agent-ready fix prompt** from those findings, to paste into your next iteration.
- **Restores your files** to the checkpoint when you need it.
It **warns** you; it does not silently block your work. An optional pre-commit hook can reject a commit above your configured risk threshold — opt-in, tunable, and bypassable like any local Git hook.
Rules decide. Agents fix.
VibeRevert does not ask another language model whether your agent's changes look risky. Its checks are deterministic: the same inputs and configuration produce the same findings, with an inspectable reason for every flag.
When something needs attention, VibeRevert can turn those findings into an agent-ready fix prompt. The rules decide what to flag; you decide what happens next.
Roll back all of it, or only the part that went wrong
viberevert rollback restores your **local project files** — tracked, staged, and untracked, including uncommitted work — to how they were when the session started. It previews by default; --apply writes the change, and every apply first saves an emergency checkpoint you can recover from.