ai-rollback

Plan and apply repository rollbacks for faulty releases or merged PRs.

1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/svange/augint-shell --skill ai-rollback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-rollback
Source: https://github.com/svange/augint-shell/tree/main/.agents/skills/ai-rollback
Command: npx skills add https://github.com/svange/augint-shell --skill ai-rollback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rollback a bad release or revert a merged PR. Use when something broke after a merge or release. Also triggered by 'something broke', 'undo the last release', 'revert'.

Core Features & Use Cases

  • Plan and execute a repository rollback using the standardized workflow to revert changes from faulty releases or merged PRs.
  • Dry-run previews to study impact before applying changes, with explicit user confirmation required for non-dry-run execution.
  • Seamless integration with existing CI/CD pipelines, allowing teams to revert changes while preserving migration/infrastructure notes when present.

Quick Start

Provide the PR number or commit SHA (or --dry-run) to plan and execute a rollback.

Frequently Asked Questions about ai-rollback

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

FAQPage Schema
How do I revert a faulty release or a merged PR in Git?

To revert a faulty release or a merged PR, you can use a standardized plan and apply rollback workflow. This process coordinates repository recovery and requires explicit user confirmation before applying any modifications to your codebase.

Can I preview a Git rollback before applying changes to the repository?

Yes, you can preview a Git rollback by using a dry-run. A dry-run allows you to study the impact of reverting a faulty release or merged PR on your repository before any actual changes are applied, ensuring safe execution.

What is the best way to automate reverting a broken release in CI/CD pipelines?

The best way to automate reverting a broken release in CI/CD pipelines is using an automated rollback workflow that supports dry-run previews and explicit confirmation. This seamlessly integrates with existing pipelines while preserving infrastructure notes.

How do I undo the last release while preserving migration notes?

You can undo the last release while preserving migration notes by executing a repository rollback workflow. This reverts the faulty changes from merged PRs while integrating with your CI/CD pipeline to retain important infrastructure and migration details.

Does the repository rollback workflow require manual confirmation?

Yes, the repository rollback workflow requires explicit user confirmation before applying changes. This safety measure ensures that non-dry-run executions, which revert faulty releases or merged PRs, only happen when explicitly approved by the user.