rollback-changes

Rollback changes by providing a changes log JSON file with phase details, file modifications, and git commits. The Skill restores modified files from backups, deletes created files, reverts commands, and undoes git commits, then generates an audit report of actions taken.

A changes log requires phase name, timestamp, files_modified, files_created, commands_executed, and git_commits. Optional fields include artifacts, plan_files, and metadata. The Skill validates the JSON structure before proceeding with restoration.

Yes, rollback automatically reverts git commits recorded in the changes log. If commit reversal is possible, it executes the undo; otherwise, it flags limitations in the rollback report for manual review.

Files created during the failed phase are deleted during rollback. Modified files are restored from backups. The Skill generates a detailed report showing all restoration actions and any warnings encountered.

Yes, rollback applies across bug fixes, security patches, refactoring, and other workflow stages. It uses the same changes log structure and restoration logic regardless of phase type or complexity.

The Skill requests confirmation before executing restoration steps and generates an audit trail report documenting all actions, warnings, and any limitations. Review the report to assess manual intervention needs.