rollback

Revert implementation commits to a pre-implementation state with git.

2|1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/FourthWiz/claude_dev_workflow --skill rollback-fourthwiz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rollback
Source: https://github.com/FourthWiz/claude_dev_workflow/tree/main/dev-workflow/skills/rollback
Command: npx skills add https://github.com/FourthWiz/claude_dev_workflow --skill rollback-fourthwiz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rollback provides a safe, auditable way to undo implementation work by mapping commits to plan tasks, showing exactly what will change, and requiring explicit confirmation before making any code modifications.

Core Features & Use Cases

  • Commit-to-task mapping: Read the current plan and correlate commits to specific tasks so rollbacks target the right work.
  • Flexible rollback scopes: Support full-phase rollbacks, selective task reverts, and single-commit undos with clear previews of affected files and dependencies.
  • Safety and governance: Stash uncommitted changes, prefer git revert for shared branches, avoid force-pushes, and log the rollback in session artifacts; useful for undoing a mistaken feature, reverting API changes, or recovering from a bad deployment.
  • Cross-repo and migration awareness: Highlight database migrations and cross-repository impacts and advise on down-migrations or coordinated rollbacks when needed.

Quick Start

Ask the rollback skill to preview and revert the last two implemented tasks for <task-name> on the current branch, showing commits, affected files, and required confirmations.

Frequently Asked Questions about rollback

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely revert git commits mapped to specific plan tasks?

To safely revert git commits, map implementation commits to plan tasks, preview affected files, stash uncommitted changes, and use git revert or reset with explicit confirmation to avoid data loss.

What is the best way to undo a merged PR without force-pushing?

The best way to undo a merged PR without force-pushes is using git revert on shared branches. This creates new commits that inversely apply changes, maintaining branch history and preventing data loss.

Can I revert code changes across multiple repositories simultaneously?

Yes, you can revert code changes across multiple repositories. The rollback process highlights cross-repo impacts, maps commits to plan tasks, and advises on coordinated rollbacks to ensure synchronized version control.

How do I undo the last commit on a local feature branch safely?

To undo the last commit on a local feature branch safely, the process stashes uncommitted changes, previews affected files, and applies git reset or revert based on whether the branch is shared.

Does reverting implementation changes handle database migrations?

Yes, reverting implementation changes handles database migrations by highlighting migration impacts during the preview phase and advising on required down-migrations before executing the git revert or reset operations.

When should I use git revert instead of git reset for rollbacks?

You should use git revert instead of git reset for shared branches or merged PRs to avoid force-pushes. Git reset is reserved for local branches where rewriting history is safe and won't impact collaborators.