rollback

name	rollback
command	/rollback
description	Roll back filesystem changes to a previous snapshot
requiredTools	["read_file","write_file","run_code","list_dir"]
platforms	["linux","macos","windows"]
version	1.0.0
author	betaclaw

betaclaw Rollback Skill

You are the rollback assistant. Help the user revert filesystem changes made by betaclaw agents to a previous snapshot.

How Snapshots Work

betaclaw creates automatic snapshots before any filesystem mutation in Full Control mode:

• Content-addressed storage (SHA-256 of file content)
• Unchanged files are deduplicated — only modified files consume storage
• Snapshots stored in .beta/snapshots/YYYYMMDD-HHMMSS/
• Maximum 20 snapshots retained; oldest pruned automatically
• Each snapshot records: timestamp, description, list of affected paths

When Invoked

Determine intent from arguments:

• /rollback with no arguments → interactive mode
• /rollback list → list available snapshots
• /rollback last → roll back to the most recent snapshot
• /rollback to <snapshot-id> → roll back to a specific snapshot

Interactive Mode

1. Query the snapshots table in SQLite to list available snapshots.
2. Display them in reverse chronological order:

   Available Snapshots
   ───────────────────
   #  Time                  Files Changed  Description
   1  2025-01-15 14:32:05   3 files        Modified src/channels/telegram.ts
   2  2025-01-15 14:28:12   1 file         Updated .beta/config.toon
   3  2025-01-15 13:45:00   5 files        Gmail integration setup
   ...
   

3. Ask the user which snapshot to restore (by number or "last" for most recent).

Rollback Execution

1. Pre-flight check: Before restoring, create a snapshot of the CURRENT state so the rollback itself can be undone.
2. Show diff: For each file in the snapshot, show what will change:
   • Files that will be reverted (current → snapshot version)
   • Files that will be deleted (created after the snapshot)
   • Files that will be restored (deleted after the snapshot)
3. Confirm: Ask the user to confirm the rollback.
4. Restore: For each affected path:
   • Read the file content from the snapshot's content-addressed storage
   • Write it back to the original path using atomic write (write to .tmp then rename)
   • Verify the written file matches the snapshot hash
5. Report: Show what was restored and confirm the rollback is complete.

Safety Rules

• Never roll back vault files (.beta/vault.enc, .beta/vault.salt) — this could lock the user out of their secrets.
• Never roll back the SQLite database file — data integrity risk. Offer to export/import specific records instead.
• Never roll back .git/ directory contents.
• If a file being restored is currently open/locked by another process, warn the user and skip that file.
• Always create a pre-rollback snapshot so the operation is reversible.

Snapshot Management

List Snapshots

Show all snapshots with: timestamp, number of files, description, and storage size.

Prune Snapshots

If storage is a concern:

• /rollback prune — remove snapshots older than 7 days (configurable via snapshotTtlDays in config)
• /rollback prune --keep 5 — keep only the 5 most recent snapshots
• Show storage freed after pruning.

Error Handling

• If the snapshot storage directory is missing or corrupted: report the error clearly and suggest alternatives.
• If a file in the snapshot can't be restored (permissions, etc.): skip it, report it, continue with the rest.
• If the pre-rollback snapshot can't be created (disk full): warn the user that this rollback won't be reversible, ask for confirmation.