undo
Skill1 starsChanged 29 days agoMITView on GitHub
Undo the file changes of an agent turn with Turnback, including shell commands and untracked files, when the user requests a restore or invokes Turnback undo.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- laz3rjenkins/atomic-commitstheir own version, first seen Nov 8, 2026
- buildomator/buildomatortheir own version, first seen Nov 4, 2026
- nguyenthanhtat/screen1-claudetheir own version, first seen Nov 1, 2026
- manastalukdar/ai-devstudiotheir own version, first seen Oct 13, 2026
- kks0488/vibe-claudetheir own version, first seen Oct 11, 2026
- hailneed/agent-blackboxtheir own version, first seen Aug 19, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- buildomator/buildomator★ 102same name
- kks0488/vibe-claude★ 29same name
- hereinthehive/kickstart★ 4same name
- nguyenthanhtat/screen1-claude★ 2same name
- manastalukdar/ai-devstudio★ 1same name
- hailneed/agent-blackbox★ 0same name
- laz3rjenkins/atomic-commits★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Call restore with target and, if the user named files, paths.
- Very specific: line 13
Ask the user to confirm. Only after a clear yes, call restore again with the same arguments plus token set to confirm_token.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Restore project files with the turnback MCP tools from this plugin. Always pass workspace set to the current project directory.
- Call
list_turnswithlimit5. If the user's request or invocation arguments name a turn ID, use it; otherwise use the newest turn. Tell the user which turn: its time, agent, prompt, and changed file count. If the user wants to keep part of the turn, callturn_stepsand use therefof the first step to undo as thetarget; that returns the files to just before that step. If the user only wants one file or folder back (for example one deleted several turns ago), callrecover_filewith itspathand use the returnedtargetandpathsinstead. - Call
restorewithtargetand, if the user named files,paths. This call only returns a plan and aconfirm_token; nothing is written yet. - Show the plan: files to rewrite, delete, or recreate. Point out actions marked
uncertain; those files may contain the user's own edits. - Ask the user to confirm. Only after a clear yes, call
restoreagain with the same arguments plustokenset toconfirm_token. - Report restored, skipped, and failed files and the safety snapshot. Files you read earlier in this conversation may have changed: read them again before editing. The user can reverse this with the
redotool.
If MCP is unavailable, resolve the installed plugin root from PLUGIN_ROOT (Codex) or CLAUDE_PLUGIN_ROOT (Claude Code) and run node <plugin-root>/dist/cli.js in the project directory. Quote the resolved path for the current shell. Use undo --dry-run for the latest turn, restore <turn> --dry-run for a named turn, or recover <path> --dry-run for one file or folder. Preserve any requested --path or --before-step. Show the plan and, after confirmation, run the same command with --yes instead of --dry-run. If the plugin root cannot be resolved, report that the integration is unavailable.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

