upgrade-cleanup SKILL.md skillA
upgrade-cleanup from ombulabs/claude-code_rails-upgrade-skill is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ombulabs/claude-code_rails-upgrade-skill/upgrade-cleanup@git:20260430.903cd29Pins git:20260430.903cd29 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ombulabs/claude-code_rails-upgrade-skill
- Path
upgrade-cleanup/upgrade-cleanup/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260430.903cd29, committed Apr 30, 2026
- Size
- 3,304 bytes
- Repository stars
- 398
- License
- MIT
Clean up after (or abandon) a Rails upgrade. Drop NextRails.next? and NextRails.current? branches and retire dual-boot scaffolding (Gemfile.next, Gemfile.next.lock, conditional Gemfile groups), keeping either the next or the current version. Trigger when the user says they are done with the upgrade, want to clean up dual-boot, want to drop NextRails branches, want to finish the upgrade, want to abandon or revert the upgrade attempt, want to roll back to the current Rails version, or want to…
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
# Upgrade Cleanup Skill Companion to the `rails-upgrade` plugin. Runs the cleanup pass that removes dual-boot scaffolding and aligns the codebase to the new version baseline. When activated, follow the workflow in `workflows/upgrade-cleanup-workflow.md` end-to-end. **Before any destructive step, confirm direction with the user** (Phase 0 Step 1): are they keeping the **next** version (finishing the upgrade) or keeping the **current** version (abandoning or pausing this hop)? Every subsequent step branches on that answer. To detect the next version, read the `Gemfile` (look for the `if NextRails.next?` / `else` block; the `next?` branch holds the upgraded-to version) or `Gemfile.next.lock`. Do NOT rely on `Gemfile.lock` alone, since during dual-boot it still pins the current version. ## When to Run Run when the user has explicitly decided to **end the dual-boot phase** in one of two directions: - **Keep next**: upgrade is done (final hop or stopping point), drop the `else` / current branches. - **Keep current**: abandoning or pausing this hop, drop the `if NextRails.next?` / next branches and `Gemfile.next*`. …
Read the whole file at its exact version.
How to install
mdr add ombulabs/claude-code_rails-upgrade-skill/upgrade-cleanup@sha256:eab46b861c7996e2The line at the top of this page pins the label git:20260430.903cd29, 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_t6shtrq7ccgdjxk5)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Apr 30, 2026.
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 (3304 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
ombulabs/claude-code_rails-upgrade-skill · 398 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_t6shtrq7ccgdjxk5 GET https://markdownregistry.com/api/v1/resolve?ref=ombulabs/claude-code_rails-upgrade-skill/upgrade-cleanup GET https://markdownregistry.com/api/v1/blob/eab46b861c7996e2072c93eb8cfb635d7712559b98f477ff000e2304b6bb615c
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.