rollback
Skill4 starsChanged 9 days agoApache-2.0View on GitHub
Preview and restore the latest OASIS-tracked file checkpoint with recovery backups and explicit confirmation.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- synaptiai/agent-capability-standardtheir own version, first seen Nov 1, 2026
- harshanandak/forge-legacytheir own version, first seen Oct 17, 2026
- elfrost/ai-patchlabtheir own version, first seen Oct 13, 2026
- tejastn10/workbenchtheir own version, first seen Oct 13, 2026
- purpleeddy/claddingtheir own version, first seen Oct 11, 2026
- popup-studio-ai/bkit-claude-codetheir own version, first seen Oct 8, 2026
Used with
Projects with it also use status, ship and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkillstatus
Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.
Also in 3 projects that use this
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 3 projects that use this
SentrySkillreview
Fixture review skill.
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- suboss87/FDEOps★ 940same name
- popup-studio-ai/bkit-claude-code★ 605same name
- ww-w-ai/bkit-claude-code★ 605same name
- ww-w-ai/bkit-gemini★ 66same name
- nahid-sparktales/agent-dispatcher★ 59same name
- purpleeddy/cladding★ 16same name
- synaptiai/agent-capability-standard★ 7same name
- harshanandak/forge-legacy★ 4same name
- elfrost/ai-patchlab★ 1same name
- tejastn10/workbench★ 1same name
1 more not listed
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.
In this repository24 other files it gives its agents.
- api-developmentSkill
- code-reviewSkill
- debuggingSkill
- designSkill
- diagnoseSkill
- environment-setupSkill
- grill-meSkill
- initSkill
- mobile-developmentSkill
- planSkill
- plugin-authoringSkill
- ponytail-auditSkill
- ponytail-debtSkill
- ponytail-gainSkill
- ponytail-helpSkill
- ponytail-reviewSkill
- ponytailSkill
- runSkill
- security-reviewSkill
- ship-featureSkill
- testingSkill
- verifySkill
- web-app-developmentSkill
- workflow-authoringSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
Use existing workspace path validation and reject unsafe destinations and symbolic links.
- Distinctive: line 34
Do not execute shell commands, contact the network, or attempt to undo external side effects.
- Distinctive: line 37
No files change until confirmation.
“Common” is measured: kept by at least 6 in 10 of the 10 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
Rollback skill
Purpose
Restore file state from the latest eligible OASIS checkpoint without silently discarding the current contents or rewriting the conversation.
Inputs
- An active OASIS session with a file checkpoint
- The latest checkpoint preview
- The user's explicit second-step confirmation: /rollback confirm
Workflow
- Preview the latest checkpoint, its originating task, tracked paths, and limitations. Do not change files during preview.
- Require the user to submit /rollback confirm after reading the preview.
- Confirm the checkpoint has not changed since the preview.
- Save the current contents of every eligible existing file to the existing local recovery-backup store before restoration.
- Restore only the file state captured by the latest eligible checkpoint. Do not delete or rewrite conversation history.
- Report restored, deleted, and skipped paths, and identify the recovery backup records created.
- Explain that shell-command side effects, network operations, installs, and changes not captured by file tools are not reversed by this checkpoint operation.
Required provider capabilities
- None for the deterministic restore operation; it is handled by OASIS runtime code
- File-system access restricted to the active workspace and OASIS's recovery store
Permissions
- Preview is read-only.
- Restoration requires explicit /rollback confirm after the preview.
- Use existing workspace path validation and reject unsafe destinations and symbolic links.
- Preserve current file contents in the recovery store before restoration.
- Do not execute shell commands, contact the network, or attempt to undo external side effects.
Success criteria
- No files change until confirmation.
- The confirmed checkpoint is still the latest checkpoint.
- Current eligible files are backed up before restore.
- Restoration results, skipped paths, and limitations are reported truthfully.
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.

