rollback-changes
Automatically rollback changes from failed workflow phases using changes log files. Use when workflows fail and need to restore previous state, including file restoration, artifact cleanup, and command reversal. Use for error recovery after failed bug fixes, security patches, or refactoring operations.
When & Why to Use This Skill
The rollback-changes skill is a robust error recovery utility designed to automatically restore a system's state after failed workflow phases. By parsing a comprehensive changes log, it reverses file modifications, removes temporary artifacts, and undoes git commits, ensuring environment consistency and minimizing manual intervention during automated task failures or agentic errors.
Use Cases
- Automated Error Recovery: Automatically revert code changes and file modifications when an AI agent fails to complete a bug fix or refactoring task, ensuring the codebase returns to a known stable state.
- CI/CD Pipeline Cleanup: Clean up orphaned artifacts, temporary files, and build residues generated during unsuccessful deployment phases to maintain a clean and predictable workspace.
- State Restoration: Restore critical configuration files from backups if a sequence of automated bash commands fails to execute correctly, preventing system drift.
- Git History Management: Revert accidental or broken commits in reverse chronological order to maintain a functional repository history after failed automated security patching or refactoring operations.
| name | rollback-changes |
|---|---|
| description | Automatically rollback changes from failed workflow phases using changes log files. Use when workflows fail and need to restore previous state, including file restoration, artifact cleanup, and command reversal. Use for error recovery after failed bug fixes, security patches, or refactoring operations. |
| allowed-tools | Bash, Read, Write |
Rollback Changes
Rollback failed workflow phases by reading changes log and reversing tracked modifications.
When to Use
- Workflow phase fails and needs state restoration
- Error recovery in worker agents
- Quality gate failures requiring revert
Input
{
"changes_log_path": ".bug-changes.json",
"phase": "bug-fixing",
"confirmation_required": true
}
Changes Log Format
{
"phase": "bug-fixing",
"timestamp": "2025-10-18T14:30:00Z",
"files_modified": [{"path": "src/app.ts", "backup": ".rollback/src-app.ts.backup"}],
"files_created": ["src/new-file.ts"],
"commands_executed": ["pnpm install", "pnpm build"],
"git_commits": ["abc123"],
"artifacts": [".bug-fixing-plan.json"]
}
Process
1. Read & Parse Changes Log
Use Read tool to load JSON. Validate required fields: phase, timestamp, files_modified, files_created, commands_executed, git_commits.
2. Request Confirmation (if required)
Show summary of changes to revert. If user declines, return dry run result.
3. Restore Modified Files
cp "{backup}" "{path}" # For each {path, backup} in files_modified
4. Delete Created Files
rm -f "{file}" # For each file in files_created
5. Revert Commands
pnpm install→ re-run to restore lockfilegit add *→git restore --staged .pnpm build→rm -rf dist/- Other → log warning (cannot auto-revert)
6. Revert Git Commits
git revert --no-edit {sha} # In reverse order
7. Cleanup Artifacts
Remove plan files and temporary artifacts.
Output
{
"success": true,
"phase": "bug-fixing",
"actions_taken": ["Restored src/app.ts", "Deleted src/new-file.ts", "Reverted abc123"],
"files_restored": 1,
"files_deleted": 1,
"git_commits_reverted": 1,
"errors": [],
"warnings": ["Backup not found: .rollback/file.backup (skipped)"]
}
Error Handling
- Missing log: Return error "Changes log not found"
- Invalid JSON: Return parsing error
- Backup not found: Log warning, continue (partial rollback OK)
- Git conflicts: Log error with manual instructions, continue
Safety Features
- Confirmation by default before any changes
- Partial rollback acceptable (documented in warnings)
- Never delete without verifying backup exists
- All actions logged for audit trail
Worker Integration
Workers should track changes during operations:
- Create
.{domain}-changes.jsonbefore modifications - Create backups in
.rollback/for modified files - Log all file creates, commands, and commits
- On failure: invoke rollback-changes with confirmation_required=false