agentleFS
FAHTHIZFAHTHIZ/oasis/skills/rollback/SKILL.md

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

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.
  • AnthropicSkill

    status

    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

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 3 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 3 projects that use this

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
  1. Distinctive:

    Use existing workspace path validation and reject unsafe destinations and symbolic links.

    line 32
  2. Distinctive:

    Do not execute shell commands, contact the network, or attempt to undo external side effects.

    line 34
  3. Distinctive:

    No files change until confirmation.

    line 37

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Preview the latest checkpoint, its originating task, tracked paths, and limitations. Do not change files during preview.
  2. Require the user to submit /rollback confirm after reading the preview.
  3. Confirm the checkpoint has not changed since the preview.
  4. Save the current contents of every eligible existing file to the existing local recovery-backup store before restoration.
  5. Restore only the file state captured by the latest eligible checkpoint. Do not delete or rewrite conversation history.
  6. Report restored, deleted, and skipped paths, and identify the recovery backup records created.
  7. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.