What problem does it solve? When an agent creates or modifies components incorrectly, manually tracking and reverting every file change is error-prone. This Skill reverses the most recent transaction by restoring backups, reverting manifest entries, and cleaning up orphaned files. ## Core Features & Use Cases - Transaction-Based Rollback: Identifies the last transaction (or a specified transaction ID) and reverts all associated file operations and manifest changes. - Verification and Reporting: Validates restored file states and manifest integrity, then reports per-operation success or failure. - Selective Rollback: Supports rolling back individual operations within batch transactions. - Use Case: After the developer agent creates an agent definition, task file, and manifest update that turn out to be wrong, run the rollback to remove the new files and restore the manifest to its prior state in one operation. ## Quick Start Ask the agent to undo the last component creation and confirm the rollback when shown the transaction details.