mcpbeat

Upgrade Cleanup

ombulabs/upgrade-cleanup

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 pause this upgrade hop. Based on FastRuby.io's "Finishing an Upgrade" methodology, extended with an abandon/pause path.

5k tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
374
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/ombulabs/claude-code_rails-upgrade-skill --skill upgrade-cleanup

The instruction itself

6 sections, as written by the author

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*.

Either way the previous parallel branch must no longer be needed (no rollback window). Deployment to production is not a hard prerequisite.

Ownership and Delegations

This skill owns the cleanup. Phase 1 below is the step list to follow. The dual-boot skill's workflows/cleanup-workflow.md is older optional reading; if it drifts from this workflow, this workflow wins.

  • Dual-boot scaffolding removal: performed here in Phase 1.
  • load_defaults alignment: out of scope. The rails-upgrade skill handles this via its rails-load-defaults step before cleanup runs.

Critical Rules

  • Do NOT leave NextRails.next? or NextRails.current? branches in the tree. That is the failure mode this skill exists to prevent.
  • Do NOT start removing branches before confirming direction. Keeping the wrong side throws away the work the user wants to keep. If the user has not stated next vs current, ask.

Workflow

See workflows/upgrade-cleanup-workflow.md for the full process: a pre-flight check, dual-boot scaffolding removal, old-version code retirement, CI and Ruby pin alignment, final verification, and the cleanup PR.

Reference

  • Finishing an Upgrade, FastRuby.io
  • workflows/upgrade-cleanup-workflow.md, full workflow
  • The dual-boot plugin's workflows/cleanup-workflow.md, optional reading for context. This skill's Phase 1 is the step list to follow, do not use dual-boot's version when it conflicts.

How to use it

Copy the folder

Take ombulabs/upgrade-cleanup from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.