vibe-rollback-plan SKILL.md skillA
vibe-rollback-plan from ash1794/vibe-engineering is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ash1794/vibe-engineering/vibe-rollback-plan@git:20261007.24cccadPins git:20261007.24cccad in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ash1794/vibe-engineering
- Path
plugins/vibe-engineering/skills/vibe-rollback-plan/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261007.24cccad, committed Oct 7, 2026
- First version recorded
- Sep 25, 2026
- Size
- 2,099 bytes
- Repository stars
- 165
- License
- MIT
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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 …
Read the whole file at its exact version.
How to install
mdr add ash1794/vibe-engineering/vibe-rollback-plan@sha256:a784902b50e2b3a5The line at the top of this page pins the label git:20261007.24cccad, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_noetuoxnrronfgi4)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 25, 2026 and Oct 7, 2026, about one every 12 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261007.24cccad latest | 2026-10-07 | 24cccad | 2,099 B | A | view · diff |
| git:20260925.f6554ff | 2026-09-25 | f6554ff | 1,946 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2099 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
ash1794/vibe-engineering · 165 stars · license MIT · pushed 2026-10-07 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_noetuoxnrronfgi4 GET https://markdownregistry.com/api/v1/resolve?ref=ash1794/vibe-engineering/vibe-rollback-plan GET https://markdownregistry.com/api/v1/blob/a784902b50e2b3a5095bf90081aefed70e80877e0506bc9933336d3dd1aed587
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.