Agent skill

Vibe Rollback Plan

by ash1794 in ash1794/vibe-engineering

Documents rollback procedures before making risky changes. An agent skill from ash1794/vibe-engineering.

MITAuto-check passedDevOps & Cloud

Install Vibe Rollback Plan

skills CLI
$ npx skills add ash1794/vibe-engineering --skill vibe-rollback-plan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ash1794/vibe-engineering vibe-rollback-plan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-rollback-plan .claude/skills/vibe-rollback-plan && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
vibe-rollback-plan
GitHub stars
163
Token cost
~525 tokens
SKILL.md length
208 words
Files
1
Skills in repo
33
Repo updated
First seen
Licence
MIT

At a glance

Documents rollback procedures before making risky changes. An agent skill from ash1794/vibe-engineering.

  • Works in 5 steps: Document the change → Define success criteria → Assess blast radius → …
  • Tasks that involve Database migrations
  • SKILL.md covers When to Use This Skill, When NOT to Use This Skill, Steps and Output Format
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Vibe Rollback Plan is an agent skill from ash1794/vibe-engineering. Documents rollback procedures before making risky changes. Covers what's changing, verification steps, rollback procedures, and blast radius assessment. Use before database migrations, breaking API changes, infrastructure or DNS changes, large dependency upgrades, or any change where undo is not obvious.

Its SKILL.md is about 530 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Database migrations. The repository describes itself as: 33 engineering discipline skills for Claude Code, OpenAI Codex & Gemini CLI + a CLI for CI/CD enforcement. Extracted from real-world multi-agent system development. Born from… The licence is MIT.

When your agent uses it

  • Tasks that involve Database migrations

Example prompts

  • “Use the vibe-rollback-plan skill to document rollback procedures before making risky changes. An agent skill from ash1794/vibe-engineering”
  • “/vibe-rollback-plan”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Document the change
  2. Define success criteria
  3. Assess blast radius
  4. Write rollback procedure
  5. Pre-change checklist

What it can do on your machine

Read from SKILL.md and the folder at commit 8f1d71b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Vibe Rollback Plan loads about 525 tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 208 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~81
When it runs · the whole SKILL.md, loaded when a task matches
~525

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ash1794/vibe-engineering at commit 8f1d71b, republished under its MIT licence (© ash1794). 208 words, ~525 tokens.

Download SKILL.mdSave it as .claude/skills/vibe-rollback-plan/SKILL.md (or your agent's skills folder).
name
vibe-rollback-plan
description
Documents rollback procedures before making risky changes. Covers what's changing, verification steps, rollback procedures, and blast radius assessment. Use before database migrations, breaking API changes, infrastructure or DNS changes, large dependency upgrades, or any change where undo is not obvious.
user-invocable
true

vibe-rollback-plan

The time to plan a rollback is BEFORE you need one.

When to Use This Skill

  • Database migrations (especially destructive ones)
  • API breaking changes
  • Infrastructure changes (networking, permissions, DNS)
  • Large dependency upgrades
  • Any change where "undo" isn't obvious

When NOT to Use This Skill

  • Safe, easily reversible changes (adding a new file, adding a feature flag)
  • Changes with automated rollback (CI/CD with rollback built in)
  • Local development changes

Steps

  1. Document the change:

    • What is being changed?
    • Why is it being changed?
    • What systems are affected?
  2. Define success criteria:

    • How do we know the change worked?
    • What metrics to watch?
    • How long to monitor before declaring success?
  3. Assess blast radius:

    • What breaks if this fails?
    • Which users/services are affected?
    • Is there data loss risk?
  4. Write rollback procedure:

    • Step-by-step commands to reverse the change
    • Expected time to rollback
    • Who needs to be notified?
  5. Pre-change checklist:

    • Rollback procedure documented
    • Rollback tested (if possible)
    • Monitoring in place
    • Team notified
    • Backup taken

Output Format

Rollback Plan: [Change Name]

Change: [Description] Risk Level: Low / Medium / High / Critical Blast Radius: [What's affected] Estimated Recovery Time: [Time to rollback]

Success Criteria
  1. [How to verify the change worked]
Rollback Procedure
bash
# Step 1: [Description]
[command]
# Step 2: [Description]
[command]
Pre-Change Checklist
  • Backup taken
  • Rollback tested
  • Monitoring active
  • Team notified

© ash1794, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/vibe-engineering/skills/vibe-rollback-plan of ash1794/vibe-engineering.

Open the folder on GitHubat commit 8f1d71b

Compare with similar skills

Vibe Rollback Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Vibe Rollback Plan compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vibe Rollback Plan this skillash1794/vibe-engineering163—~525Automated safety check: PassMIT
Learningskortix-ai/suna20k—~1.1kAutomated safety check: PassCustom licence
Database Migrations Migration Observabilityaiskillstore/marketplace4337 repos~3.4kAutomated safety check: PassNone
Rollbacksoftspark/ai-toolkit179—~1.3kAutomated safety check: NotesApache-2.0
Database Migration Reviewrohitg00/ai-engineering-from-scratch66k—~315Automated safety check: PassMIT
Kortix Rollbackkortix-ai/suna20k—~2.1kAutomated safety check: PassCustom licence

Similar skills

  • Learnings

    kortix-ai/suna

    The project's episodic memory: a timestamped ledger of rules paid for with real outages and near-misses, one entry per incident.

    20k GitHub stars~1.1k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Migration monitoring, CDC, and observability infrastructure. An agent skill from aiskillstore/marketplace.

    433 GitHub starsUsed in 7 repos~3.4k tokens
    DevOps & CloudAuto-check passed
  • Rollback

    softspark/ai-toolkit

    Rolls back git commit, DB migration, or deploy to known-good with safety + health checks.

    179 GitHub stars~1.3k tokensUpdated 2 days ago
    DevOps & CloudAuto-check: notes
  • Database Migration Review

    rohitg00/ai-engineering-from-scratch

    Reviews database migration files before merge, collecting forward, rollback, locking and data-safety evidence, with a decision that is blocked whenever evidence is missing.

    66k GitHub stars~315 tokensUpdated today
    DatabasesAuto-check passed
  • Kortix Rollback

    kortix-ai/suna

    How to roll Kortix PRODUCTION back to an older already-released version — the inverse of a release.

    20k GitHub stars~2.1k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Wp Migration Upgrade Review

    jorgerosal/wordpress-skills

    WordPress migration and upgrade review. An agent skill from jorgerosal/wordpress-skills.

    103 GitHub stars~1.1k tokensUpdated 4 mo ago
    DatabasesAuto-check passed

More from ash1794/vibe-engineering

All 33 skills in this repo
  • Vibe Concurrent Test Safety

    ash1794/vibe-engineering

    Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering.

    163 GitHub stars~665 tokensUpdated 3 days ago
    Auto-check passed
  • Vibe Fuzz Parser Inputs

    ash1794/vibe-engineering

    Generates fuzz test scaffolding for parsers handling external input (YAML, JSON, config files, user input).

    163 GitHub stars~722 tokensUpdated 3 days ago
    Auto-check passed
  • Vibe Golden File Testing

    ash1794/vibe-engineering

    Implements snapshot/golden file tests with temporal normalization so tests don't break daily.

    163 GitHub stars~669 tokensUpdated 3 days ago
    Auto-check passed
  • Vibe Parallel Task Decomposition

    ash1794/vibe-engineering

    Analyzes large tasks for independent subtasks that can be safely parallelized.

    163 GitHub stars~717 tokensUpdated 3 days ago
    Auto-check passed
  • Vibe Slop Filter

    ash1794/vibe-engineering

    Strips AI-generation "smell" from prose before it ships (READMEs, docs, release notes, PR descriptions, posts, emails).

    163 GitHub stars~2.3k tokensUpdated 3 days ago
    Auto-check passed
  • Vibe Spec Sync

    ash1794/vibe-engineering

    Keeps specification documents and code in agreement. An agent skill from ash1794/vibe-engineering.

    163 GitHub stars~2.2k tokensUpdated 3 days ago
    Auto-check passed

Questions about Vibe Rollback Plan

What does Vibe Rollback Plan do?

Documents rollback procedures before making risky changes. An agent skill from ash1794/vibe-engineering. Vibe Rollback Plan is an agent skill from ash1794/vibe-engineering. Documents rollback procedures before making risky changes.

When should I use Vibe Rollback Plan?

Vibe Rollback Plan fits situations like: tasks that involve Database migrations.

How do I install Vibe Rollback Plan in Claude Code?

Run `npx skills add ash1794/vibe-engineering --skill vibe-rollback-plan -a claude-code`. Or copy the skill folder (plugins/vibe-engineering/skills/vibe-rollback-plan in ash1794/vibe-engineering) into .claude/skills/vibe-rollback-plan in your project. Claude Code loads it when a task matches its description.

How do I install Vibe Rollback Plan in Codex?

Run `npx skills add ash1794/vibe-engineering --skill vibe-rollback-plan -a codex`. Or copy the skill folder (plugins/vibe-engineering/skills/vibe-rollback-plan in ash1794/vibe-engineering) into .agents/skills/vibe-rollback-plan in your project. Codex loads it when a task matches its description.

Can I use Vibe Rollback Plan in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ash1794/vibe-engineering --skill vibe-rollback-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vibe-rollback-plan, .gemini/skills/vibe-rollback-plan, .github/skills/vibe-rollback-plan and .opencode/skills/vibe-rollback-plan in your project.

What does Vibe Rollback Plan need to run?

SKILL.md names no scripts, command-line tools or credentials: Vibe Rollback Plan is instructions for the agent only.

Does Vibe Rollback Plan access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Vibe Rollback Plan safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Vibe Rollback Plan use?

Vibe Rollback Plan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Vibe Rollback Plan use?

About 525 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Vibe Rollback Plan?

Skills that share tags, products or a category with Vibe Rollback Plan: Learnings (kortix-ai/suna, 20k stars), Database Migrations Migration Observability (aiskillstore/marketplace, 433 stars), Rollback (softspark/ai-toolkit, 179 stars) and Database Migration Review (rohitg00/ai-engineering-from-scratch, 66k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vibe Rollback Plan?

ash1794 (a GitHub user) maintains it in ash1794/vibe-engineering, which has 163 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 7, 2026.

Source: ash1794/vibe-engineering on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.