What problem does it solve? Rolling back a Git branch to a previous commit or tag is risky: reset rewrites history, force pushes can break collaborators, and mistakes are hard to undo. This Skill provides a safe, interactive rollback workflow that previews every command before executing, creates backup branches, and requires explicit user confirmation for destructive operations. ## Core Features & Use Cases - Interactive rollback flow: Lists branches and recent versions (git log, tags, reflog), then lets the user pick the branch, target revision, and mode (reset or revert) before anything executes. - Dry-run by default: Prints the full command sequence without executing; reset operations require explicit confirmation and automatically create a timestamped backup branch first. - Protected branch safeguards: Extra confirmation for main, master, release/*, and production branches; never force-pushes or pushes automatically, only suggests commands for the user to run. - Use Case: A bad commit was pushed to a release branch. Use this Skill to preview a revert plan, confirm the reverse commits, and roll back safely while keeping history intact for collaborators. ## Quick Start Ask the assistant to roll back the branch release/v2 to tag v2.0.5 using revert mode with a dry-run preview first.