ombulabs/claude-code_rails-upgrade-skill / rails-upgrade
rails-upgrade
VerifiedAnalyzes Rails applications and generates comprehensive upgrade reports with breaking changes, deprecations, and step-by-step migration guides for Rails 2.3 through 8.1. Use when upgrading Rails applications, planning multi-hop upgrades, querying version-specific changes, or answering what stands between the app and the next Rails version. Based on FastRuby.io methodology and "The Complete Guide to Upgrade Rails" ebook.
workflows/03-validate-upgrade-path-workflow.md
View on GitHub# Workflow 03: Validate Upgrade Path
**Purpose:** Confirm the requested upgrade is a single hop or a planned sequence of hops. Version skipping is not allowed.
**When to use:** After Workflow 02, before dual-boot setup (Workflow 04), so the hop is settled before `Gemfile.next` pins anything.
## Inputs
- Exact current Rails version (from Workflow 00)
- Target Rails version (from the user)
## Outputs
- Single-hop or multi-hop decision
- The list of individual hops, in order
## Gates (must be true before the next workflow that runs)
- Every hop is one adjacent minor/major step
## Step 1: Check if upgrade is single-hop or multi-hop
Compare the exact current version (Workflow 00) with the target the user named. One adjacent minor or major step (7.0 to 7.1, 7.2 to 8.0) is a single hop. Anything further (5.2 to 8.1) is multi-hop. Read `references/sequential-strategy-reference.md` for the supported paths table and the Ruby requirement of each hop.
## Step 2: If multi-hop, explain sequential requirement
Tell the user that Rails upgrades MUST follow a sequential path and that version skipping is not allowed, with the examples from `references/sequential-strategy-reference.md` (5.2 to 6.1 skips 6.0; 7.0 to 8.0 skips 7.1 and 7.2). Then: break it into individual hops, generate separate reports for each hop, and recommend completing each hop fully before moving to the next.
## Step 3: Plan individual hops
List the hops in order (e.g. 5.2 → 6.0 → 6.1 → 7.0 → 7.1 → 7.2 → 8.0 → 8.1). For each hop note the Ruby requirement from the supported paths table. For the hop-by-hop plan, milestones and time budget, read `references/multi-hop-strategy-reference.md`, section "Planning a Multi-Hop Upgrade". Workflows 04 to 12 then run once per hop; Workflows 00 to 02 run again at the start of every hop.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |