dev-rollback

Delete release tags, revert main merges, and create hotfix branches.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/learnzdevelopmenthub/paadhai --skill dev-rollback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-rollback
Source: https://github.com/learnzdevelopmenthub/paadhai/tree/main/.claude/skills/dev-rollback
Command: npx skills add https://github.com/learnzdevelopmenthub/paadhai --skill dev-rollback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A failed release tag on main can leave production in an unrecoverable state while developers scramble to revert merges manually. This Skill orchestrates a controlled rollback by deleting release artifacts, reverting the merge commit, and staging a hotfix branch so the team can continue work without guessing the necessary steps.

Core Features & Use Cases

  • Detection and assessment: Verifies that the chosen tag exists, locates the merge commit on main, and reports downstream commits plus develop divergence to gauge impact.
  • Safe execution plan: Deletes the GitHub Release, removes the tag locally and remotely, reverts the merge on the main branch, and pushes each change while stopping on failure.
  • Hotfix preparation: Creates and pushes a fix branch using the configured fix prefix and version so a clean workspace is ready for the next fix.

Quick Start

Use the dev-rollback skill to confirm the failed release version, delete its tag, revert the merge, and branch for the hotfix.

Frequently Asked Questions about dev-rollback

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

FAQPage Schema
How do I rollback a failed release tag on the main branch in git?

A failed release rollback involves deleting the GitHub Release, removing the tag locally and remotely, and reverting the merge commit on the main branch. This sequence removes the bad artifacts and restores the previous stable production state.

What steps are required to prepare a hotfix branch after reverting a bad release?

Preparing a hotfix branch after reverting a bad release requires creating a new branch from the corrected main branch using a configured fix prefix and version. This provides a clean, isolated workspace to develop and push the necessary production fix.

How do I assess the impact of reverting a merge commit on the develop branch?

Assessing the impact of reverting a merge commit involves checking downstream commits on the main branch and evaluating the divergence between the main and develop branches. This analysis helps gauge how the rollback affects ongoing development work.

Do I need the gh CLI and a configuration file to automate a production rollback?

Yes, automating a production rollback requires the gh CLI for GitHub Release deletion and a configuration file like .paadhai.json. This file provides the necessary branch names, owners, and version prefixes to execute the rollback safely.

Can I automate reverting a bad release without manual confirmation?

No, automating a bad release rollback requires an explicit confirmation gate before deleting tags or reverting merges. This safety mechanism prevents accidental data loss and ensures operators intentionally authorize the destructive rollback actions.