Creator · ombulabs
Last updated · Sep 5, 2026
Analyzes 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, or querying version-specific changes. Base
Creator · ombulabs
Last updated · Sep 5, 2026
Analyzes 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, or querying version-specific changes. Base
Creator · ombulabs
Last updated · Sep 5, 2026
Analyzes 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, or querying version-specific changes. Base
Creator · ombulabs
Last updated · Sep 5, 2026
Analyzes 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, or querying version-specific changes. Base
Do not auto-install
Install targets
Codex install prompt
Install the "rails-upgrade" agent skill from https://github.com/ombulabs/claude-code_rails-upgrade-skill/tree/main/rails-upgrade. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Analyzes 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, or querying version-specific changes. Based on FastRuby.io methodology and "The Complete Guide to Upgrade Rails" ebook. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"ombulabs-rails-upgrade","task":"Install rails-upgrade","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
Research agents
I need my agent to research a topic, compare sources, and produce a concise report.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add ombulabs/claude-code_rails-upgrade-skill --skill rails-upgrade
Maintenance
fresh
11d since push
Risk
Needs review
Dependency or permission surface needs review
GitHub quality
381
73/100 Quality · 66/100 Trust
Coverage tags
Review notes
Dependency or permission surface needs review · Permission surface may require sandboxing
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
StrongSolid option that is likely worth shortlisting for production workflows.
Trust
Do not auto-installTrust Score v5 found insufficient evidence for agent installation. Treat this as discovery material, not an executable recommendation.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Choose a stronger alternative or inspect the source manually before any install attempt.
Stars
381 GitHub stars
Repo activity
381 stars, 15 forks
Maintenance
11d since push
License
MIT
Install
npx skills add ombulabs/claude-code_rails-upgrade-skill --skill rails-upgrade
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add ombulabs/claude-code_rails-upgrade-skill --skill rails-upgradeDo not use when
Alternative
1.9K Stars
npx skills add yanliudesign/mono-color-skill --skill mono-color
Alternative
61.0K Stars
npx skills add mvanhorn/last30days-skill -g
Alternative
38.4K Stars
npx skills add Imbad0202/academic-research-skills
Alternative
256.3K Stars
npx skills add mattpocock/skills --skill grill-me
Agent safety v2
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
Test manually in an isolated workspace and compare against safer alternatives.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
medium
Skill may inspect schemas, query databases, or work with persistent stores.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20rails-upgrade%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20rails-upgrade%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/ombulabs-rails-upgrade/install
Agent should check
Copy prompt
Task: Use rails-upgrade in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20rails-upgrade%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/ombulabs-rails-upgrade/install
Install command: npx skills add ombulabs/claude-code_rails-upgrade-skill --skill rails-upgrade
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/ombulabs-rails-upgrade/install
LLM text format
/api/skills/ombulabs-rails-upgrade/install?format=text
Find alternatives
/api/skills/search?q=rails-upgrade&limit=3
Agent prompt
Use rails-upgrade for this task. Review https://www.openagentskill.com/api/skills/ombulabs-rails-upgrade/install, then install with: npx skills add ombulabs/claude-code_rails-upgrade-skill --skill rails-upgradeRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/ombulabs-rails-upgrade
LLM text
/api/registry/manifest/ombulabs-rails-upgrade?format=text
Install alias
/api/registry/install/ombulabs-rails-upgrade
Recommend
/api/registry/recommend?task=Use%20rails-upgrade%20in%20an%20agent%20workflow&limit=3
Agent fit
GitHub automation
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Shortlist this skill and compare it with close alternatives before production adoption.
Role in stack
Companion skill
Primary fit
GitHub automation
Trust label
Strong shortlist
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Trust Score v5 found insufficient evidence for agent installation. Treat this as discovery material, not an executable recommendation.
GitHub adoption
INFO381 GitHub stars
Stars/forks activity
CHECK381 stars, 15 forks; issue activity unavailable in current metadata
Recent maintenance
PASS11d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Choose a stronger alternative or inspect the source manually before any install attempt.
Quality profile
Solid option that is likely worth shortlisting for production workflows.
Workflow fit
Manage repositories
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Build and ship code
I need a coding agent that can understand a repository, edit code, and review pull requests.
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Workflow fit
Inspect, patch, and verify code
A workflow for software agents that inspect repositories, review pull requests, generate tests, and turn findings into shippable patches.
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Ingest, retrieve, and cite
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Alternative shortlist
Similar skills that may fit this task.
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
Academic Research Skills for Claude Code: research → write → review → revise → finalize
A relentless interview to sharpen a plan or design.
--- name: rails-upgrade description: Analyzes 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, or querying version-specific changes. Based on FastRuby.io methodology and "The Complete Guide to Upgrade Rails" ebook. ---
# Rails Upgrade Assistant Skill
## Skill Identity - **Name:** Rails Upgrade Assistant - **Purpose:** Intelligent Rails application upgrades from 2.3 through 8.1 - **Skill Type:** Modular with external workflows and examples - **Upgrade Strategy:** Sequential only (no version skipping) - **Methodology:** Based on FastRuby.io upgrade best practices and "The Complete Guide to Upgrade Rails" ebook - **Attribution:** Content based on "The Complete Guide to Upgrade Rails" by FastRuby.io (OmbuLabs)
---
## Dependencies
- **dual-boot skill** ([github.com/ombulabs/claude-code_dual-boot-skill](https://github.com/ombulabs/claude-code_dual-boot-skill)) — Sets up and manages dual-boot environments using the `next_rails` gem. Covers setup, `NextRails.next?` code patterns, CI configuration, and post-upgrade cleanup. Must be installed for Step 2 of the upgrade workflow. - **rails-load-defaults skill** ([github.com/ombulabs/claude-code_rails-load-defaults-skill](https://github.com/ombulabs/claude-code_rails-load-defaults-skill)) — Handles incremental `load_defaults` updates with tiered risk assessment (Tier 1: low-risk, Tier 2: needs codebase grep, Tier 3: requires human review). Used as the final step after the Rails version upgrade is complete.
---
## Core Methodology (FastRuby.io Approach)
This skill follows the proven FastRuby.io upgrade methodology:
1. **Incremental Upgrades** - Always upgrade one minor/major version at a time 2. **Assessment First** - Understand scope before making changes 3. **Dual-Boot Testing** - Test both versions during transition using `next_rails` gem 4. **Test Coverage** - Ensure adequate test coverage before upgrading (aim for 80%+) 5. **Gem Compatibility** - Check gem compatibility at each step using RailsBump 6. **Deprecation Warnings** - Address deprecations before upgrading 7. **Backwards Compatible Changes** - Deploy small changes to production before version bump
**Key Resources:** - **DELEGATE** to the `dual-boot` skill for dual-boot setup with `next_rails` (see Dependencies) - See `references/deprecation-warnings.md` for managing deprecations - See `references/staying-current.md` for maintaining upgrades over time
---
## CRITICAL: Dual-Boot Code Pattern with `NextRails.next?`
When proposing code fixes that must work with both the current and target Rails versions (dual-boot), **always use `NextRails.next?` from the `next_rails` gem** — never use `respond_to?` or other feature-detection patterns.
**DELEGATE** to the `dual-boot` skill for: - Setup and initialization (`next_rails --init`, `Gemfile.next`) - `NextRails.next?` code patterns and examples - CI configuration for dual-boot testing - Post-upgrade cleanup (removing dual-boot branches)
**DEPENDENCY:** Requires the [dual-boot skill](https://github.com/ombulabs/claude-code_dual-boot-skill)
---
## Trigger Patterns
Claude should activate this skill when user says:
**Upgrade Requests:** - "Upgrade my Rails app to [version]" - "Help me upgrade from Rails [x] to [y]" - "What breaking changes are in Rails [version]?" - "Plan my upgrade from [x] to [y]" - "What Rails version am I using?" - "Analyze my Rails app for upgrade" - "Find breaking changes in my code" - "Check my app for Rails [version] compatibility"
**Specific Report Requests:** - "Show me the app:update changes" - "Preview configuration changes for Rails [version]" - "Generate the upgrade report" - "What will change if I upgrade?"
**Upgrade Cleanup Requests (delegate to the `upgrade-cleanup` plugin):** - "Finish the upgrade" - "Clean up after my Rails upgrade" - "Remove the dual-boot setup" - "Drop the NextRails branches" - "We're done upgrading to Rails [version]"
---
## CRITICAL: Sequential Upgrade Strategy
### ⚠️ Version Skipping is NOT Allowed
Rails upgrades MUST follow a sequential path. Examples:
**For Rails 5.x to 8.x:** ``` 5.0.x → 5.1.x → 5.2.x → 6.0.x → 6.1.x → 7.0.x → 7.1.x → 7.2.x → 8.0.x → 8.1.x ```
**You CANNOT skip versions.** Examples: - ❌ 5.2 → 6.1 (skips 6.0) - ❌ 6.0 → 7.0 (skips 6.1) - ❌ 7.0 → 8.0 (skips 7.1 and 7.2) - ✅ 5.2 → 6.0 (correct) - ✅ 7.0 → 7.1 (correct) - ✅ 7.2 → 8.0 (correct)
If user requests a multi-hop upgrade (e.g., 5.2 → 8.1): 1. Explain the sequential requirement 2. Break it into individual hops 3. Generate separate reports for each hop 4. Recommend completing each hop fully before moving to next
---
## Supported Upgrade Paths
### Legacy Rails (2.3 - 4.2)
| From | To | Difficulty | Key Changes | Ruby Required | |------|-----|-----------|-------------|---------------| | 2.3.x | 3.0.x | Very Hard | XSS protection, routes syntax | 1.8.7 - 1.9.3 | | 3.0.x | 3.1.x | Medium | Asset pipeline, jQuery | 1.8.7 - 1.9.3 | | 3.1.x | 3.2.x | Easy | Ruby 1.9.3 support | 1.8.7 - 2.0 | | 3.2.x | 4.0.x | Hard | Strong Parameters, Turbolinks | 1.9.3+ | | 4.0.x | 4.1.x | Medium | Spring, secrets.yml | 1.9.3+ | | 4.1.x | 4.2.x | Medium | ActiveJob, Web Console | 1.9.3+ | | 4.2.x | 5.0.x | Hard | ActionCable, API mode, ApplicationRecord | 2.2.2+ |
### Modern Rails (5.0 - 8.1)
| From | To | Difficulty | Key Changes | Ruby Required | |------|-----|-----------|-------------|---------------| | 5.0.x | 5.1.x | Easy | Encrypted secrets, yarn default | 2.2.2+ | | 5.1.x | 5.2.x | Medium | Active Storage, credentials | 2.2.2+ | | 5.2.x | 6.0.x | Hard | Zeitwerk, Action Mailbox/Text | 2.5.0+ | | 6.0.x | 6.1.x | Medium | Horizontal sharding, strict loading | 2.5.0+ | | 6.1.x | 7.0.x | Hard | Hotwire/Turbo, Import Maps | 2.7.0+ | | 7.0.x | 7.1.x | Medium | Composite keys, async queries | 2.7.0+ | | 7.1.x | 7.2.x | Medium | Transaction-aware jobs, DevContainers | 3.1.0+ | | 7.2.x | 8.0.x | Very Hard | Propshaft, Solid gems, Kamal | 3.2.0+ | | 8.0.x | 8.1.x | Easy | Bundler-audit, max_connections | 3.2.0+ |
---
## Available Resources
### Core Documentation - `SKILL.md` - This file (entry point)
### Version-Specific Guides (Load as needed)
**Legacy Rails:** - `version-guides/upgrade-3.2-to-4.0.md` - Rails 3.2 → 4.0 (Strong Parameters) - `version-guides/upgrade-4.0-to-4.1.md` - Rails 4.0 → 4.1 (Spring, secrets.yml, enums) - `version-guides/upgrade-4.1-to-4.2.md` - Rails 4.1 → 4.2 (ActiveJob, Web Console) - `version-guides/upgrade-4.2-to-5.0.md` - Rails 4.2 → 5.0 (ApplicationRecord)
**Modern Rails:** - `version-guides/upgrade-5.0-to-5.1.md` - Rails 5.0 → 5.1 (Encrypted secrets) - `version-guides/upgrade-5.1-to-5.2.md` - Rails 5.1 → 5.2 (Active Storage, Credentials) - `version-guides/upgrade-5.2-to-6.0.md` - Rails 5.2 → 6.0 (Zeitwerk) - `version-guides/upgrade-6.0-to-6.1.md` - Rails 6.0 → 6.1 (Horizontal sharding) - `version-guides/upgrade-6.1-to-7.0.md` - Rails 6.1 → 7.0 (Hotwire/Turbo) - `version-guides/upgrade-7.0-to-7.1.md` - Rails 7.0 → 7.1 (Composite keys) - `version-guides/upgrade-7.1-to-7.2.md` - Rails 7.1 → 7.2 (Transaction jobs) - `version-guides/upgrade-7.2-to-8.0.md` - Rails 7.2 → 8.0 (Propshaft) - `version-guides/upgrade-8.0-to-8.1.md` - Rails 8.0 → 8.1 (bundler-audit)
### Workflow Guides (Load when generating deliverables) - `workflows/test-suite-verification-workflow.md` - **MANDATORY FIRST STEP** - How to run and verify test suite - `workflows/no-test-suite-smoke-workflow.md` - **Load from Step 1 when no runnable RSpec/Minitest suite exists** - Rails boot, routes, migration-status, and build smoke baseline with partial-confidence reporting - `workflows/direct-detection-workflow.md` - How to run breaking change detection directly - `workflows/upgrade-report-workflow.md` - How to generate upgrade reports - `workflows/gem-compatibility-workflow.md` - **Load in Step 4.5** - Per-lockfile gem compatibility check against the target Rails version. Documents both the primary (`next_rails` `bundle_report compatibility`) and the secondary (railsbump.org API) and the rules for when to escalate. - `workflows/boot-smoke-test-workflow.md` - **Load in Step 4.6** - Run a Rails-loading command against `Gemfile.next` to catch gem-level runtime incompat that the resolver can't see (gems calling removed Rails internals or `require`-ing removed files). - `workflows/ci-sync-workflow.md` - **MANDATORY before opening the upgrade PR** - How to verify CI config matches the upgraded Gemfile - `workflows/app-update-preview-workflow.md` - How to generate app:update previews - **`upgrade-cleanup` companion plugin** - User-triggered. Removes dual-boot scaffolding and drops `NextRails.next?` / `NextRails.current?` branches. Deprecation triage stays with this skill for the next hop.
### Examples (Load when user needs clarification) - `examples/simple-upgrade.md` - Single-hop upgrade example - `examples/multi-hop-upgrade.md` - Multi-hop upgrade example
### External Dependencies - **dual-boot skill** - Dual-boot setup and management with next_rails (Step 2) (https://github.com/ombulabs/claude-code_dual-boot-skill) - **rails-load-defaults skill** - Incremental load_defaults alignment (Step 7, final step) (https://github.com/ombulabs/claude-code_rails-load-defaults-skill)
### Reference Materials - `references/deprecation-warnings.md` - Finding and fixing deprecations - `references/staying-current.md` - Keeping up with Rails releases - `references/breaking-changes-by-version.md` - Quick lookup - `references/multi-hop-strategy.md` - Multi-version planning - `references/testing-checklist.md` - Comprehensive testing - `references/gem-compatibility.md` - Gem update order and the "no compatible version" playbook (fork / vendor / replace). Load only when Step 4.5's compatibility check produced blockers. - `references/js-compressor-sprockets-mismatch.md` - Keeping terser / closure-compiler working when the target Rails pins Sprockets to the 2.x line. Load only when JS_COMPRESSOR_GEM_MISMATCH fires.
### Detection Pattern Resources - `detection-scripts/patterns/rails-*.yml` - Version-specific patterns for direct detection
### Report Templates - `templates/upgrade-report-template.md` - Main upgrade report structure - `templates/app-update-preview-template.md` - Configuration preview
---
## High-Level Workflow
When user requests an upgrade, follow this workflow:
### Step 0: Verify Latest Patch Version (MANDATORY PRE-STEP) ``` ⚠️ THIS STEP IS REQUIRED BEFORE ANY OTHER WORK
1. Read Gemfile.lock to find exact current Rails version (e.g., 3.2.19) 2. Compare against latest patch for that series: - EOL series (≤ 7.1): use static table in references/multi-hop-strategy.md - Active series (≥ 7.2): query RubyGems API (see references/multi-hop-strategy.md for commands) 3. If current version < latest patch: - INFORM user: "Your app is on Rails X.Y.Z but the latest patch is X.Y.W" - Guide through Gemfile update and bundle update rails - Run test suite after patch upgrade - Deploy patch upgrade before proceeding - Do NOT proceed to next minor/major until on latest patch 4. If current version == latest patch: - Proceed to Step 1 ```
**Why patch first:** Patch releases contain security fixes, bug fixes, and additional deprecation warnings. Starting the version hop on the latest patch is safer (the security fixes are already in production) and easier to debug (the new deprecation warnings surface issues that would otherwise show up mid-upgrade).
### Step 1: Run Test Suite (MANDATORY FIRST STEP) ``` ⚠️ THIS STEP IS REQUIRED BEFORE ANY OTHER WORK
1. Read: workflows/test-suite-verification-workflow.md 2. Detect test framework (RSpec, Minitest, or both) 3. Run test suite with: bundle exec rspec OR bundle exec rails test 4. Capture results: total tests, passing, failing, pending 5. If no runnable test suite exists: - Load: work
Source provenance
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for rails-upgrade, ready for a manual X post.
rails-upgrade: Analyzes Rails applications and generates comprehensive upgrade reports with breaking changes... 381 stars https://www.openagentskill.com/skills/ombulabs-rails-upgrade?ref=x
Listing + install path for rails-upgrade: https://www.openagentskill.com/skills/ombulabs-rails-upgrade?ref=x Install: npx skills add ombulabs/claude-code_rails-upgrade-skill --skill rails-upgrade
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to ombulabs but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/ombulabs-rails-upgrade?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/ombulabs-rails-upgrade?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/ombulabs-rails-upgrade/audit)
[](https://www.openagentskill.com/skills/ombulabs-rails-upgrade?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)ombulabs
@ombulabs
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Do not auto-install
mono-color
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
1.9K StarsLast30days Skill
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
61.0K StarsAcademic Research Skills
Academic Research Skills for Claude Code: research → write → review → revise → finalize
38.4K Starsgrill-me
A relentless interview to sharpen a plan or design.
256.3K StarsDo not auto-install
Install targets
Codex install prompt
Install the "rails-upgrade" agent skill from https://github.com/ombulabs/claude-code_rails-upgrade-skill/tree/main/rails-upgrade. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Analyzes 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, or querying version-specific changes. Based on FastRuby.io methodology and "The Complete Guide to Upgrade Rails" ebook. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"ombulabs-rails-upgrade","task":"Install rails-upgrade","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
Research agents
I need my agent to research a topic, compare sources, and produce a concise report.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add ombulabs/claude-code_rails-upgrade-skill --skill rails-upgrade
Maintenance
fresh
11d since push
Risk
Needs review
Dependency or permission surface needs review
GitHub quality
381
73/100 Quality · 66/100 Trust
Coverage tags
Review notes
Dependency or permission surface needs review · Permission surface may require sandboxing
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
StrongSolid option that is likely worth shortlisting for production workflows.
Trust
Do not auto-installTrust Score v5 found insufficient evidence for agent installation. Treat this as discovery material, not an executable recommendation.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Choose a stronger alternative or inspect the source manually before any install attempt.
Stars
381 GitHub stars
Repo activity
381 stars, 15 forks
Maintenance
11d since push
License
MIT
Install
npx skills add ombulabs/claude-code_rails-upgrade-skill --skill rails-upgrade
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add ombulabs/claude-code_rails-upgrade-skill --skill rails-upgradeDo not use when
Alternative
1.9K Stars
npx skills add yanliudesign/mono-color-skill --skill mono-color
Alternative
61.0K Stars
npx skills add mvanhorn/last30days-skill -g
Alternative
38.4K Stars
npx skills add Imbad0202/academic-research-skills
Alternative
256.3K Stars
npx skills add mattpocock/skills --skill grill-me
Agent safety v2
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
Test manually in an isolated workspace and compare against safer alternatives.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
medium
Skill may inspect schemas, query databases, or work with persistent stores.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20rails-upgrade%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20rails-upgrade%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/ombulabs-rails-upgrade/install
Agent should check
Copy prompt
Task: Use rails-upgrade in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20rails-upgrade%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/ombulabs-rails-upgrade/install
Install command: npx skills add ombulabs/claude-code_rails-upgrade-skill --skill rails-upgrade
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/ombulabs-rails-upgrade/install
LLM text format
/api/skills/ombulabs-rails-upgrade/install?format=text
Find alternatives
/api/skills/search?q=rails-upgrade&limit=3
Agent prompt
Use rails-upgrade for this task. Review https://www.openagentskill.com/api/skills/ombulabs-rails-upgrade/install, then install with: npx skills add ombulabs/claude-code_rails-upgrade-skill --skill rails-upgradeRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/ombulabs-rails-upgrade
LLM text
/api/registry/manifest/ombulabs-rails-upgrade?format=text
Install alias
/api/registry/install/ombulabs-rails-upgrade
Recommend
/api/registry/recommend?task=Use%20rails-upgrade%20in%20an%20agent%20workflow&limit=3
Agent fit
GitHub automation
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Shortlist this skill and compare it with close alternatives before production adoption.
Role in stack
Companion skill
Primary fit
GitHub automation
Trust label
Strong shortlist
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Trust Score v5 found insufficient evidence for agent installation. Treat this as discovery material, not an executable recommendation.
GitHub adoption
INFO381 GitHub stars
Stars/forks activity
CHECK381 stars, 15 forks; issue activity unavailable in current metadata
Recent maintenance
PASS11d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Choose a stronger alternative or inspect the source manually before any install attempt.
Quality profile
Solid option that is likely worth shortlisting for production workflows.
Workflow fit
Manage repositories
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Build and ship code
I need a coding agent that can understand a repository, edit code, and review pull requests.
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Workflow fit
Inspect, patch, and verify code
A workflow for software agents that inspect repositories, review pull requests, generate tests, and turn findings into shippable patches.
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Ingest, retrieve, and cite
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Alternative shortlist
Similar skills that may fit this task.
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
Academic Research Skills for Claude Code: research → write → review → revise → finalize
A relentless interview to sharpen a plan or design.
--- name: rails-upgrade description: Analyzes 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, or querying version-specific changes. Based on FastRuby.io methodology and "The Complete Guide to Upgrade Rails" ebook. ---
# Rails Upgrade Assistant Skill
## Skill Identity - **Name:** Rails Upgrade Assistant - **Purpose:** Intelligent Rails application upgrades from 2.3 through 8.1 - **Skill Type:** Modular with external workflows and examples - **Upgrade Strategy:** Sequential only (no version skipping) - **Methodology:** Based on FastRuby.io upgrade best practices and "The Complete Guide to Upgrade Rails" ebook - **Attribution:** Content based on "The Complete Guide to Upgrade Rails" by FastRuby.io (OmbuLabs)
---
## Dependencies
- **dual-boot skill** ([github.com/ombulabs/claude-code_dual-boot-skill](https://github.com/ombulabs/claude-code_dual-boot-skill)) — Sets up and manages dual-boot environments using the `next_rails` gem. Covers setup, `NextRails.next?` code patterns, CI configuration, and post-upgrade cleanup. Must be installed for Step 2 of the upgrade workflow. - **rails-load-defaults skill** ([github.com/ombulabs/claude-code_rails-load-defaults-skill](https://github.com/ombulabs/claude-code_rails-load-defaults-skill)) — Handles incremental `load_defaults` updates with tiered risk assessment (Tier 1: low-risk, Tier 2: needs codebase grep, Tier 3: requires human review). Used as the final step after the Rails version upgrade is complete.
---
## Core Methodology (FastRuby.io Approach)
This skill follows the proven FastRuby.io upgrade methodology:
1. **Incremental Upgrades** - Always upgrade one minor/major version at a time 2. **Assessment First** - Understand scope before making changes 3. **Dual-Boot Testing** - Test both versions during transition using `next_rails` gem 4. **Test Coverage** - Ensure adequate test coverage before upgrading (aim for 80%+) 5. **Gem Compatibility** - Check gem compatibility at each step using RailsBump 6. **Deprecation Warnings** - Address deprecations before upgrading 7. **Backwards Compatible Changes** - Deploy small changes to production before version bump
**Key Resources:** - **DELEGATE** to the `dual-boot` skill for dual-boot setup with `next_rails` (see Dependencies) - See `references/deprecation-warnings.md` for managing deprecations - See `references/staying-current.md` for maintaining upgrades over time
---
## CRITICAL: Dual-Boot Code Pattern with `NextRails.next?`
When proposing code fixes that must work with both the current and target Rails versions (dual-boot), **always use `NextRails.next?` from the `next_rails` gem** — never use `respond_to?` or other feature-detection patterns.
**DELEGATE** to the `dual-boot` skill for: - Setup and initialization (`next_rails --init`, `Gemfile.next`) - `NextRails.next?` code patterns and examples - CI configuration for dual-boot testing - Post-upgrade cleanup (removing dual-boot branches)
**DEPENDENCY:** Requires the [dual-boot skill](https://github.com/ombulabs/claude-code_dual-boot-skill)
---
## Trigger Patterns
Claude should activate this skill when user says:
**Upgrade Requests:** - "Upgrade my Rails app to [version]" - "Help me upgrade from Rails [x] to [y]" - "What breaking changes are in Rails [version]?" - "Plan my upgrade from [x] to [y]" - "What Rails version am I using?" - "Analyze my Rails app for upgrade" - "Find breaking changes in my code" - "Check my app for Rails [version] compatibility"
**Specific Report Requests:** - "Show me the app:update changes" - "Preview configuration changes for Rails [version]" - "Generate the upgrade report" - "What will change if I upgrade?"
**Upgrade Cleanup Requests (delegate to the `upgrade-cleanup` plugin):** - "Finish the upgrade" - "Clean up after my Rails upgrade" - "Remove the dual-boot setup" - "Drop the NextRails branches" - "We're done upgrading to Rails [version]"
---
## CRITICAL: Sequential Upgrade Strategy
### ⚠️ Version Skipping is NOT Allowed
Rails upgrades MUST follow a sequential path. Examples:
**For Rails 5.x to 8.x:** ``` 5.0.x → 5.1.x → 5.2.x → 6.0.x → 6.1.x → 7.0.x → 7.1.x → 7.2.x → 8.0.x → 8.1.x ```
**You CANNOT skip versions.** Examples: - ❌ 5.2 → 6.1 (skips 6.0) - ❌ 6.0 → 7.0 (skips 6.1) - ❌ 7.0 → 8.0 (skips 7.1 and 7.2) - ✅ 5.2 → 6.0 (correct) - ✅ 7.0 → 7.1 (correct) - ✅ 7.2 → 8.0 (correct)
If user requests a multi-hop upgrade (e.g., 5.2 → 8.1): 1. Explain the sequential requirement 2. Break it into individual hops 3. Generate separate reports for each hop 4. Recommend completing each hop fully before moving to next
---
## Supported Upgrade Paths
### Legacy Rails (2.3 - 4.2)
| From | To | Difficulty | Key Changes | Ruby Required | |------|-----|-----------|-------------|---------------| | 2.3.x | 3.0.x | Very Hard | XSS protection, routes syntax | 1.8.7 - 1.9.3 | | 3.0.x | 3.1.x | Medium | Asset pipeline, jQuery | 1.8.7 - 1.9.3 | | 3.1.x | 3.2.x | Easy | Ruby 1.9.3 support | 1.8.7 - 2.0 | | 3.2.x | 4.0.x | Hard | Strong Parameters, Turbolinks | 1.9.3+ | | 4.0.x | 4.1.x | Medium | Spring, secrets.yml | 1.9.3+ | | 4.1.x | 4.2.x | Medium | ActiveJob, Web Console | 1.9.3+ | | 4.2.x | 5.0.x | Hard | ActionCable, API mode, ApplicationRecord | 2.2.2+ |
### Modern Rails (5.0 - 8.1)
| From | To | Difficulty | Key Changes | Ruby Required | |------|-----|-----------|-------------|---------------| | 5.0.x | 5.1.x | Easy | Encrypted secrets, yarn default | 2.2.2+ | | 5.1.x | 5.2.x | Medium | Active Storage, credentials | 2.2.2+ | | 5.2.x | 6.0.x | Hard | Zeitwerk, Action Mailbox/Text | 2.5.0+ | | 6.0.x | 6.1.x | Medium | Horizontal sharding, strict loading | 2.5.0+ | | 6.1.x | 7.0.x | Hard | Hotwire/Turbo, Import Maps | 2.7.0+ | | 7.0.x | 7.1.x | Medium | Composite keys, async queries | 2.7.0+ | | 7.1.x | 7.2.x | Medium | Transaction-aware jobs, DevContainers | 3.1.0+ | | 7.2.x | 8.0.x | Very Hard | Propshaft, Solid gems, Kamal | 3.2.0+ | | 8.0.x | 8.1.x | Easy | Bundler-audit, max_connections | 3.2.0+ |
---
## Available Resources
### Core Documentation - `SKILL.md` - This file (entry point)
### Version-Specific Guides (Load as needed)
**Legacy Rails:** - `version-guides/upgrade-3.2-to-4.0.md` - Rails 3.2 → 4.0 (Strong Parameters) - `version-guides/upgrade-4.0-to-4.1.md` - Rails 4.0 → 4.1 (Spring, secrets.yml, enums) - `version-guides/upgrade-4.1-to-4.2.md` - Rails 4.1 → 4.2 (ActiveJob, Web Console) - `version-guides/upgrade-4.2-to-5.0.md` - Rails 4.2 → 5.0 (ApplicationRecord)
**Modern Rails:** - `version-guides/upgrade-5.0-to-5.1.md` - Rails 5.0 → 5.1 (Encrypted secrets) - `version-guides/upgrade-5.1-to-5.2.md` - Rails 5.1 → 5.2 (Active Storage, Credentials) - `version-guides/upgrade-5.2-to-6.0.md` - Rails 5.2 → 6.0 (Zeitwerk) - `version-guides/upgrade-6.0-to-6.1.md` - Rails 6.0 → 6.1 (Horizontal sharding) - `version-guides/upgrade-6.1-to-7.0.md` - Rails 6.1 → 7.0 (Hotwire/Turbo) - `version-guides/upgrade-7.0-to-7.1.md` - Rails 7.0 → 7.1 (Composite keys) - `version-guides/upgrade-7.1-to-7.2.md` - Rails 7.1 → 7.2 (Transaction jobs) - `version-guides/upgrade-7.2-to-8.0.md` - Rails 7.2 → 8.0 (Propshaft) - `version-guides/upgrade-8.0-to-8.1.md` - Rails 8.0 → 8.1 (bundler-audit)
### Workflow Guides (Load when generating deliverables) - `workflows/test-suite-verification-workflow.md` - **MANDATORY FIRST STEP** - How to run and verify test suite - `workflows/no-test-suite-smoke-workflow.md` - **Load from Step 1 when no runnable RSpec/Minitest suite exists** - Rails boot, routes, migration-status, and build smoke baseline with partial-confidence reporting - `workflows/direct-detection-workflow.md` - How to run breaking change detection directly - `workflows/upgrade-report-workflow.md` - How to generate upgrade reports - `workflows/gem-compatibility-workflow.md` - **Load in Step 4.5** - Per-lockfile gem compatibility check against the target Rails version. Documents both the primary (`next_rails` `bundle_report compatibility`) and the secondary (railsbump.org API) and the rules for when to escalate. - `workflows/boot-smoke-test-workflow.md` - **Load in Step 4.6** - Run a Rails-loading command against `Gemfile.next` to catch gem-level runtime incompat that the resolver can't see (gems calling removed Rails internals or `require`-ing removed files). - `workflows/ci-sync-workflow.md` - **MANDATORY before opening the upgrade PR** - How to verify CI config matches the upgraded Gemfile - `workflows/app-update-preview-workflow.md` - How to generate app:update previews - **`upgrade-cleanup` companion plugin** - User-triggered. Removes dual-boot scaffolding and drops `NextRails.next?` / `NextRails.current?` branches. Deprecation triage stays with this skill for the next hop.
### Examples (Load when user needs clarification) - `examples/simple-upgrade.md` - Single-hop upgrade example - `examples/multi-hop-upgrade.md` - Multi-hop upgrade example
### External Dependencies - **dual-boot skill** - Dual-boot setup and management with next_rails (Step 2) (https://github.com/ombulabs/claude-code_dual-boot-skill) - **rails-load-defaults skill** - Incremental load_defaults alignment (Step 7, final step) (https://github.com/ombulabs/claude-code_rails-load-defaults-skill)
### Reference Materials - `references/deprecation-warnings.md` - Finding and fixing deprecations - `references/staying-current.md` - Keeping up with Rails releases - `references/breaking-changes-by-version.md` - Quick lookup - `references/multi-hop-strategy.md` - Multi-version planning - `references/testing-checklist.md` - Comprehensive testing - `references/gem-compatibility.md` - Gem update order and the "no compatible version" playbook (fork / vendor / replace). Load only when Step 4.5's compatibility check produced blockers. - `references/js-compressor-sprockets-mismatch.md` - Keeping terser / closure-compiler working when the target Rails pins Sprockets to the 2.x line. Load only when JS_COMPRESSOR_GEM_MISMATCH fires.
### Detection Pattern Resources - `detection-scripts/patterns/rails-*.yml` - Version-specific patterns for direct detection
### Report Templates - `templates/upgrade-report-template.md` - Main upgrade report structure - `templates/app-update-preview-template.md` - Configuration preview
---
## High-Level Workflow
When user requests an upgrade, follow this workflow:
### Step 0: Verify Latest Patch Version (MANDATORY PRE-STEP) ``` ⚠️ THIS STEP IS REQUIRED BEFORE ANY OTHER WORK
1. Read Gemfile.lock to find exact current Rails version (e.g., 3.2.19) 2. Compare against latest patch for that series: - EOL series (≤ 7.1): use static table in references/multi-hop-strategy.md - Active series (≥ 7.2): query RubyGems API (see references/multi-hop-strategy.md for commands) 3. If current version < latest patch: - INFORM user: "Your app is on Rails X.Y.Z but the latest patch is X.Y.W" - Guide through Gemfile update and bundle update rails - Run test suite after patch upgrade - Deploy patch upgrade before proceeding - Do NOT proceed to next minor/major until on latest patch 4. If current version == latest patch: - Proceed to Step 1 ```
**Why patch first:** Patch releases contain security fixes, bug fixes, and additional deprecation warnings. Starting the version hop on the latest patch is safer (the security fixes are already in production) and easier to debug (the new deprecation warnings surface issues that would otherwise show up mid-upgrade).
### Step 1: Run Test Suite (MANDATORY FIRST STEP) ``` ⚠️ THIS STEP IS REQUIRED BEFORE ANY OTHER WORK
1. Read: workflows/test-suite-verification-workflow.md 2. Detect test framework (RSpec, Minitest, or both) 3. Run test suite with: bundle exec rspec OR bundle exec rails test 4. Capture results: total tests, passing, failing, pending 5. If no runnable test suite exists: - Load: work
Source provenance
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for rails-upgrade, ready for a manual X post.
rails-upgrade: Analyzes Rails applications and generates comprehensive upgrade reports with breaking changes... 381 stars https://www.openagentskill.com/skills/ombulabs-rails-upgrade?ref=x
Listing + install path for rails-upgrade: https://www.openagentskill.com/skills/ombulabs-rails-upgrade?ref=x Install: npx skills add ombulabs/claude-code_rails-upgrade-skill --skill rails-upgrade
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to ombulabs but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/ombulabs-rails-upgrade?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/ombulabs-rails-upgrade?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/ombulabs-rails-upgrade/audit)
[](https://www.openagentskill.com/skills/ombulabs-rails-upgrade?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)ombulabs
@ombulabs
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Do not auto-install
mono-color
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
1.9K StarsLast30days Skill
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
61.0K StarsAcademic Research Skills
Academic Research Skills for Claude Code: research → write → review → revise → finalize
38.4K Starsgrill-me
A relentless interview to sharpen a plan or design.
256.3K StarsDo not auto-install
Install targets
Codex install prompt
Install the "rails-upgrade" agent skill from https://github.com/ombulabs/claude-code_rails-upgrade-skill/tree/main/rails-upgrade. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Analyzes 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, or querying version-specific changes. Based on FastRuby.io methodology and "The Complete Guide to Upgrade Rails" ebook. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"ombulabs-rails-upgrade","task":"Install rails-upgrade","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
Research agents
I need my agent to research a topic, compare sources, and produce a concise report.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add ombulabs/claude-code_rails-upgrade-skill --skill rails-upgrade
Maintenance
fresh
11d since push
Risk
Needs review
Dependency or permission surface needs review
GitHub quality
381
73/100 Quality · 66/100 Trust
Coverage tags
Review notes
Dependency or permission surface needs review · Permission surface may require sandboxing
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
StrongSolid option that is likely worth shortlisting for production workflows.
Trust
Do not auto-installTrust Score v5 found insufficient evidence for agent installation. Treat this as discovery material, not an executable recommendation.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Choose a stronger alternative or inspect the source manually before any install attempt.
Stars
381 GitHub stars
Repo activity
381 stars, 15 forks
Maintenance
11d since push
License
MIT
Install
npx skills add ombulabs/claude-code_rails-upgrade-skill --skill rails-upgrade
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add ombulabs/claude-code_rails-upgrade-skill --skill rails-upgradeDo not use when
Alternative
1.9K Stars
npx skills add yanliudesign/mono-color-skill --skill mono-color
Alternative
61.0K Stars
npx skills add mvanhorn/last30days-skill -g
Alternative
38.4K Stars
npx skills add Imbad0202/academic-research-skills
Alternative
256.3K Stars
npx skills add mattpocock/skills --skill grill-me
Agent safety v2
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
Test manually in an isolated workspace and compare against safer alternatives.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
medium
Skill may inspect schemas, query databases, or work with persistent stores.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20rails-upgrade%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20rails-upgrade%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/ombulabs-rails-upgrade/install
Agent should check
Copy prompt
Task: Use rails-upgrade in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20rails-upgrade%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/ombulabs-rails-upgrade/install
Install command: npx skills add ombulabs/claude-code_rails-upgrade-skill --skill rails-upgrade
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/ombulabs-rails-upgrade/install
LLM text format
/api/skills/ombulabs-rails-upgrade/install?format=text
Find alternatives
/api/skills/search?q=rails-upgrade&limit=3
Agent prompt
Use rails-upgrade for this task. Review https://www.openagentskill.com/api/skills/ombulabs-rails-upgrade/install, then install with: npx skills add ombulabs/claude-code_rails-upgrade-skill --skill rails-upgradeRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/ombulabs-rails-upgrade
LLM text
/api/registry/manifest/ombulabs-rails-upgrade?format=text
Install alias
/api/registry/install/ombulabs-rails-upgrade
Recommend
/api/registry/recommend?task=Use%20rails-upgrade%20in%20an%20agent%20workflow&limit=3
Agent fit
GitHub automation
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Shortlist this skill and compare it with close alternatives before production adoption.
Role in stack
Companion skill
Primary fit
GitHub automation
Trust label
Strong shortlist
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Trust Score v5 found insufficient evidence for agent installation. Treat this as discovery material, not an executable recommendation.
GitHub adoption
INFO381 GitHub stars
Stars/forks activity
CHECK381 stars, 15 forks; issue activity unavailable in current metadata
Recent maintenance
PASS11d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Choose a stronger alternative or inspect the source manually before any install attempt.
Quality profile
Solid option that is likely worth shortlisting for production workflows.
Workflow fit
Manage repositories
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Build and ship code
I need a coding agent that can understand a repository, edit code, and review pull requests.
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Workflow fit
Inspect, patch, and verify code
A workflow for software agents that inspect repositories, review pull requests, generate tests, and turn findings into shippable patches.
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Ingest, retrieve, and cite
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Alternative shortlist
Similar skills that may fit this task.
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
Academic Research Skills for Claude Code: research → write → review → revise → finalize
A relentless interview to sharpen a plan or design.
--- name: rails-upgrade description: Analyzes 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, or querying version-specific changes. Based on FastRuby.io methodology and "The Complete Guide to Upgrade Rails" ebook. ---
# Rails Upgrade Assistant Skill
## Skill Identity - **Name:** Rails Upgrade Assistant - **Purpose:** Intelligent Rails application upgrades from 2.3 through 8.1 - **Skill Type:** Modular with external workflows and examples - **Upgrade Strategy:** Sequential only (no version skipping) - **Methodology:** Based on FastRuby.io upgrade best practices and "The Complete Guide to Upgrade Rails" ebook - **Attribution:** Content based on "The Complete Guide to Upgrade Rails" by FastRuby.io (OmbuLabs)
---
## Dependencies
- **dual-boot skill** ([github.com/ombulabs/claude-code_dual-boot-skill](https://github.com/ombulabs/claude-code_dual-boot-skill)) — Sets up and manages dual-boot environments using the `next_rails` gem. Covers setup, `NextRails.next?` code patterns, CI configuration, and post-upgrade cleanup. Must be installed for Step 2 of the upgrade workflow. - **rails-load-defaults skill** ([github.com/ombulabs/claude-code_rails-load-defaults-skill](https://github.com/ombulabs/claude-code_rails-load-defaults-skill)) — Handles incremental `load_defaults` updates with tiered risk assessment (Tier 1: low-risk, Tier 2: needs codebase grep, Tier 3: requires human review). Used as the final step after the Rails version upgrade is complete.
---
## Core Methodology (FastRuby.io Approach)
This skill follows the proven FastRuby.io upgrade methodology:
1. **Incremental Upgrades** - Always upgrade one minor/major version at a time 2. **Assessment First** - Understand scope before making changes 3. **Dual-Boot Testing** - Test both versions during transition using `next_rails` gem 4. **Test Coverage** - Ensure adequate test coverage before upgrading (aim for 80%+) 5. **Gem Compatibility** - Check gem compatibility at each step using RailsBump 6. **Deprecation Warnings** - Address deprecations before upgrading 7. **Backwards Compatible Changes** - Deploy small changes to production before version bump
**Key Resources:** - **DELEGATE** to the `dual-boot` skill for dual-boot setup with `next_rails` (see Dependencies) - See `references/deprecation-warnings.md` for managing deprecations - See `references/staying-current.md` for maintaining upgrades over time
---
## CRITICAL: Dual-Boot Code Pattern with `NextRails.next?`
When proposing code fixes that must work with both the current and target Rails versions (dual-boot), **always use `NextRails.next?` from the `next_rails` gem** — never use `respond_to?` or other feature-detection patterns.
**DELEGATE** to the `dual-boot` skill for: - Setup and initialization (`next_rails --init`, `Gemfile.next`) - `NextRails.next?` code patterns and examples - CI configuration for dual-boot testing - Post-upgrade cleanup (removing dual-boot branches)
**DEPENDENCY:** Requires the [dual-boot skill](https://github.com/ombulabs/claude-code_dual-boot-skill)
---
## Trigger Patterns
Claude should activate this skill when user says:
**Upgrade Requests:** - "Upgrade my Rails app to [version]" - "Help me upgrade from Rails [x] to [y]" - "What breaking changes are in Rails [version]?" - "Plan my upgrade from [x] to [y]" - "What Rails version am I using?" - "Analyze my Rails app for upgrade" - "Find breaking changes in my code" - "Check my app for Rails [version] compatibility"
**Specific Report Requests:** - "Show me the app:update changes" - "Preview configuration changes for Rails [version]" - "Generate the upgrade report" - "What will change if I upgrade?"
**Upgrade Cleanup Requests (delegate to the `upgrade-cleanup` plugin):** - "Finish the upgrade" - "Clean up after my Rails upgrade" - "Remove the dual-boot setup" - "Drop the NextRails branches" - "We're done upgrading to Rails [version]"
---
## CRITICAL: Sequential Upgrade Strategy
### ⚠️ Version Skipping is NOT Allowed
Rails upgrades MUST follow a sequential path. Examples:
**For Rails 5.x to 8.x:** ``` 5.0.x → 5.1.x → 5.2.x → 6.0.x → 6.1.x → 7.0.x → 7.1.x → 7.2.x → 8.0.x → 8.1.x ```
**You CANNOT skip versions.** Examples: - ❌ 5.2 → 6.1 (skips 6.0) - ❌ 6.0 → 7.0 (skips 6.1) - ❌ 7.0 → 8.0 (skips 7.1 and 7.2) - ✅ 5.2 → 6.0 (correct) - ✅ 7.0 → 7.1 (correct) - ✅ 7.2 → 8.0 (correct)
If user requests a multi-hop upgrade (e.g., 5.2 → 8.1): 1. Explain the sequential requirement 2. Break it into individual hops 3. Generate separate reports for each hop 4. Recommend completing each hop fully before moving to next
---
## Supported Upgrade Paths
### Legacy Rails (2.3 - 4.2)
| From | To | Difficulty | Key Changes | Ruby Required | |------|-----|-----------|-------------|---------------| | 2.3.x | 3.0.x | Very Hard | XSS protection, routes syntax | 1.8.7 - 1.9.3 | | 3.0.x | 3.1.x | Medium | Asset pipeline, jQuery | 1.8.7 - 1.9.3 | | 3.1.x | 3.2.x | Easy | Ruby 1.9.3 support | 1.8.7 - 2.0 | | 3.2.x | 4.0.x | Hard | Strong Parameters, Turbolinks | 1.9.3+ | | 4.0.x | 4.1.x | Medium | Spring, secrets.yml | 1.9.3+ | | 4.1.x | 4.2.x | Medium | ActiveJob, Web Console | 1.9.3+ | | 4.2.x | 5.0.x | Hard | ActionCable, API mode, ApplicationRecord | 2.2.2+ |
### Modern Rails (5.0 - 8.1)
| From | To | Difficulty | Key Changes | Ruby Required | |------|-----|-----------|-------------|---------------| | 5.0.x | 5.1.x | Easy | Encrypted secrets, yarn default | 2.2.2+ | | 5.1.x | 5.2.x | Medium | Active Storage, credentials | 2.2.2+ | | 5.2.x | 6.0.x | Hard | Zeitwerk, Action Mailbox/Text | 2.5.0+ | | 6.0.x | 6.1.x | Medium | Horizontal sharding, strict loading | 2.5.0+ | | 6.1.x | 7.0.x | Hard | Hotwire/Turbo, Import Maps | 2.7.0+ | | 7.0.x | 7.1.x | Medium | Composite keys, async queries | 2.7.0+ | | 7.1.x | 7.2.x | Medium | Transaction-aware jobs, DevContainers | 3.1.0+ | | 7.2.x | 8.0.x | Very Hard | Propshaft, Solid gems, Kamal | 3.2.0+ | | 8.0.x | 8.1.x | Easy | Bundler-audit, max_connections | 3.2.0+ |
---
## Available Resources
### Core Documentation - `SKILL.md` - This file (entry point)
### Version-Specific Guides (Load as needed)
**Legacy Rails:** - `version-guides/upgrade-3.2-to-4.0.md` - Rails 3.2 → 4.0 (Strong Parameters) - `version-guides/upgrade-4.0-to-4.1.md` - Rails 4.0 → 4.1 (Spring, secrets.yml, enums) - `version-guides/upgrade-4.1-to-4.2.md` - Rails 4.1 → 4.2 (ActiveJob, Web Console) - `version-guides/upgrade-4.2-to-5.0.md` - Rails 4.2 → 5.0 (ApplicationRecord)
**Modern Rails:** - `version-guides/upgrade-5.0-to-5.1.md` - Rails 5.0 → 5.1 (Encrypted secrets) - `version-guides/upgrade-5.1-to-5.2.md` - Rails 5.1 → 5.2 (Active Storage, Credentials) - `version-guides/upgrade-5.2-to-6.0.md` - Rails 5.2 → 6.0 (Zeitwerk) - `version-guides/upgrade-6.0-to-6.1.md` - Rails 6.0 → 6.1 (Horizontal sharding) - `version-guides/upgrade-6.1-to-7.0.md` - Rails 6.1 → 7.0 (Hotwire/Turbo) - `version-guides/upgrade-7.0-to-7.1.md` - Rails 7.0 → 7.1 (Composite keys) - `version-guides/upgrade-7.1-to-7.2.md` - Rails 7.1 → 7.2 (Transaction jobs) - `version-guides/upgrade-7.2-to-8.0.md` - Rails 7.2 → 8.0 (Propshaft) - `version-guides/upgrade-8.0-to-8.1.md` - Rails 8.0 → 8.1 (bundler-audit)
### Workflow Guides (Load when generating deliverables) - `workflows/test-suite-verification-workflow.md` - **MANDATORY FIRST STEP** - How to run and verify test suite - `workflows/no-test-suite-smoke-workflow.md` - **Load from Step 1 when no runnable RSpec/Minitest suite exists** - Rails boot, routes, migration-status, and build smoke baseline with partial-confidence reporting - `workflows/direct-detection-workflow.md` - How to run breaking change detection directly - `workflows/upgrade-report-workflow.md` - How to generate upgrade reports - `workflows/gem-compatibility-workflow.md` - **Load in Step 4.5** - Per-lockfile gem compatibility check against the target Rails version. Documents both the primary (`next_rails` `bundle_report compatibility`) and the secondary (railsbump.org API) and the rules for when to escalate. - `workflows/boot-smoke-test-workflow.md` - **Load in Step 4.6** - Run a Rails-loading command against `Gemfile.next` to catch gem-level runtime incompat that the resolver can't see (gems calling removed Rails internals or `require`-ing removed files). - `workflows/ci-sync-workflow.md` - **MANDATORY before opening the upgrade PR** - How to verify CI config matches the upgraded Gemfile - `workflows/app-update-preview-workflow.md` - How to generate app:update previews - **`upgrade-cleanup` companion plugin** - User-triggered. Removes dual-boot scaffolding and drops `NextRails.next?` / `NextRails.current?` branches. Deprecation triage stays with this skill for the next hop.
### Examples (Load when user needs clarification) - `examples/simple-upgrade.md` - Single-hop upgrade example - `examples/multi-hop-upgrade.md` - Multi-hop upgrade example
### External Dependencies - **dual-boot skill** - Dual-boot setup and management with next_rails (Step 2) (https://github.com/ombulabs/claude-code_dual-boot-skill) - **rails-load-defaults skill** - Incremental load_defaults alignment (Step 7, final step) (https://github.com/ombulabs/claude-code_rails-load-defaults-skill)
### Reference Materials - `references/deprecation-warnings.md` - Finding and fixing deprecations - `references/staying-current.md` - Keeping up with Rails releases - `references/breaking-changes-by-version.md` - Quick lookup - `references/multi-hop-strategy.md` - Multi-version planning - `references/testing-checklist.md` - Comprehensive testing - `references/gem-compatibility.md` - Gem update order and the "no compatible version" playbook (fork / vendor / replace). Load only when Step 4.5's compatibility check produced blockers. - `references/js-compressor-sprockets-mismatch.md` - Keeping terser / closure-compiler working when the target Rails pins Sprockets to the 2.x line. Load only when JS_COMPRESSOR_GEM_MISMATCH fires.
### Detection Pattern Resources - `detection-scripts/patterns/rails-*.yml` - Version-specific patterns for direct detection
### Report Templates - `templates/upgrade-report-template.md` - Main upgrade report structure - `templates/app-update-preview-template.md` - Configuration preview
---
## High-Level Workflow
When user requests an upgrade, follow this workflow:
### Step 0: Verify Latest Patch Version (MANDATORY PRE-STEP) ``` ⚠️ THIS STEP IS REQUIRED BEFORE ANY OTHER WORK
1. Read Gemfile.lock to find exact current Rails version (e.g., 3.2.19) 2. Compare against latest patch for that series: - EOL series (≤ 7.1): use static table in references/multi-hop-strategy.md - Active series (≥ 7.2): query RubyGems API (see references/multi-hop-strategy.md for commands) 3. If current version < latest patch: - INFORM user: "Your app is on Rails X.Y.Z but the latest patch is X.Y.W" - Guide through Gemfile update and bundle update rails - Run test suite after patch upgrade - Deploy patch upgrade before proceeding - Do NOT proceed to next minor/major until on latest patch 4. If current version == latest patch: - Proceed to Step 1 ```
**Why patch first:** Patch releases contain security fixes, bug fixes, and additional deprecation warnings. Starting the version hop on the latest patch is safer (the security fixes are already in production) and easier to debug (the new deprecation warnings surface issues that would otherwise show up mid-upgrade).
### Step 1: Run Test Suite (MANDATORY FIRST STEP) ``` ⚠️ THIS STEP IS REQUIRED BEFORE ANY OTHER WORK
1. Read: workflows/test-suite-verification-workflow.md 2. Detect test framework (RSpec, Minitest, or both) 3. Run test suite with: bundle exec rspec OR bundle exec rails test 4. Capture results: total tests, passing, failing, pending 5. If no runnable test suite exists: - Load: work
Source provenance
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for rails-upgrade, ready for a manual X post.
rails-upgrade: Analyzes Rails applications and generates comprehensive upgrade reports with breaking changes... 381 stars https://www.openagentskill.com/skills/ombulabs-rails-upgrade?ref=x
Listing + install path for rails-upgrade: https://www.openagentskill.com/skills/ombulabs-rails-upgrade?ref=x Install: npx skills add ombulabs/claude-code_rails-upgrade-skill --skill rails-upgrade
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to ombulabs but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/ombulabs-rails-upgrade?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/ombulabs-rails-upgrade?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/ombulabs-rails-upgrade/audit)
[](https://www.openagentskill.com/skills/ombulabs-rails-upgrade?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)ombulabs
@ombulabs
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Do not auto-install
mono-color
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
1.9K StarsLast30days Skill
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
61.0K StarsAcademic Research Skills
Academic Research Skills for Claude Code: research → write → review → revise → finalize
38.4K Starsgrill-me
A relentless interview to sharpen a plan or design.
256.3K StarsDo not auto-install
Install targets
Codex install prompt
Install the "rails-upgrade" agent skill from https://github.com/ombulabs/claude-code_rails-upgrade-skill/tree/main/rails-upgrade. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Analyzes 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, or querying version-specific changes. Based on FastRuby.io methodology and "The Complete Guide to Upgrade Rails" ebook. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"ombulabs-rails-upgrade","task":"Install rails-upgrade","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
Research agents
I need my agent to research a topic, compare sources, and produce a concise report.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add ombulabs/claude-code_rails-upgrade-skill --skill rails-upgrade
Maintenance
fresh
11d since push
Risk
Needs review
Dependency or permission surface needs review
GitHub quality
381
73/100 Quality · 66/100 Trust
Coverage tags
Review notes
Dependency or permission surface needs review · Permission surface may require sandboxing
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
StrongSolid option that is likely worth shortlisting for production workflows.
Trust
Do not auto-installTrust Score v5 found insufficient evidence for agent installation. Treat this as discovery material, not an executable recommendation.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Choose a stronger alternative or inspect the source manually before any install attempt.
Stars
381 GitHub stars
Repo activity
381 stars, 15 forks
Maintenance
11d since push
License
MIT
Install
npx skills add ombulabs/claude-code_rails-upgrade-skill --skill rails-upgrade
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add ombulabs/claude-code_rails-upgrade-skill --skill rails-upgradeDo not use when
Alternative
1.9K Stars
npx skills add yanliudesign/mono-color-skill --skill mono-color
Alternative
61.0K Stars
npx skills add mvanhorn/last30days-skill -g
Alternative
38.4K Stars
npx skills add Imbad0202/academic-research-skills
Alternative
256.3K Stars
npx skills add mattpocock/skills --skill grill-me
Agent safety v2
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
Test manually in an isolated workspace and compare against safer alternatives.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
medium
Skill may inspect schemas, query databases, or work with persistent stores.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20rails-upgrade%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20rails-upgrade%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/ombulabs-rails-upgrade/install
Agent should check
Copy prompt
Task: Use rails-upgrade in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20rails-upgrade%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/ombulabs-rails-upgrade/install
Install command: npx skills add ombulabs/claude-code_rails-upgrade-skill --skill rails-upgrade
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/ombulabs-rails-upgrade/install
LLM text format
/api/skills/ombulabs-rails-upgrade/install?format=text
Find alternatives
/api/skills/search?q=rails-upgrade&limit=3
Agent prompt
Use rails-upgrade for this task. Review https://www.openagentskill.com/api/skills/ombulabs-rails-upgrade/install, then install with: npx skills add ombulabs/claude-code_rails-upgrade-skill --skill rails-upgradeRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/ombulabs-rails-upgrade
LLM text
/api/registry/manifest/ombulabs-rails-upgrade?format=text
Install alias
/api/registry/install/ombulabs-rails-upgrade
Recommend
/api/registry/recommend?task=Use%20rails-upgrade%20in%20an%20agent%20workflow&limit=3
Agent fit
GitHub automation
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Shortlist this skill and compare it with close alternatives before production adoption.
Role in stack
Companion skill
Primary fit
GitHub automation
Trust label
Strong shortlist
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Trust Score v5 found insufficient evidence for agent installation. Treat this as discovery material, not an executable recommendation.
GitHub adoption
INFO381 GitHub stars
Stars/forks activity
CHECK381 stars, 15 forks; issue activity unavailable in current metadata
Recent maintenance
PASS11d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Choose a stronger alternative or inspect the source manually before any install attempt.
Quality profile
Solid option that is likely worth shortlisting for production workflows.
Workflow fit
Manage repositories
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Build and ship code
I need a coding agent that can understand a repository, edit code, and review pull requests.
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Workflow fit
Inspect, patch, and verify code
A workflow for software agents that inspect repositories, review pull requests, generate tests, and turn findings into shippable patches.
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Ingest, retrieve, and cite
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Alternative shortlist
Similar skills that may fit this task.
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
Academic Research Skills for Claude Code: research → write → review → revise → finalize
A relentless interview to sharpen a plan or design.
--- name: rails-upgrade description: Analyzes 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, or querying version-specific changes. Based on FastRuby.io methodology and "The Complete Guide to Upgrade Rails" ebook. ---
# Rails Upgrade Assistant Skill
## Skill Identity - **Name:** Rails Upgrade Assistant - **Purpose:** Intelligent Rails application upgrades from 2.3 through 8.1 - **Skill Type:** Modular with external workflows and examples - **Upgrade Strategy:** Sequential only (no version skipping) - **Methodology:** Based on FastRuby.io upgrade best practices and "The Complete Guide to Upgrade Rails" ebook - **Attribution:** Content based on "The Complete Guide to Upgrade Rails" by FastRuby.io (OmbuLabs)
---
## Dependencies
- **dual-boot skill** ([github.com/ombulabs/claude-code_dual-boot-skill](https://github.com/ombulabs/claude-code_dual-boot-skill)) — Sets up and manages dual-boot environments using the `next_rails` gem. Covers setup, `NextRails.next?` code patterns, CI configuration, and post-upgrade cleanup. Must be installed for Step 2 of the upgrade workflow. - **rails-load-defaults skill** ([github.com/ombulabs/claude-code_rails-load-defaults-skill](https://github.com/ombulabs/claude-code_rails-load-defaults-skill)) — Handles incremental `load_defaults` updates with tiered risk assessment (Tier 1: low-risk, Tier 2: needs codebase grep, Tier 3: requires human review). Used as the final step after the Rails version upgrade is complete.
---
## Core Methodology (FastRuby.io Approach)
This skill follows the proven FastRuby.io upgrade methodology:
1. **Incremental Upgrades** - Always upgrade one minor/major version at a time 2. **Assessment First** - Understand scope before making changes 3. **Dual-Boot Testing** - Test both versions during transition using `next_rails` gem 4. **Test Coverage** - Ensure adequate test coverage before upgrading (aim for 80%+) 5. **Gem Compatibility** - Check gem compatibility at each step using RailsBump 6. **Deprecation Warnings** - Address deprecations before upgrading 7. **Backwards Compatible Changes** - Deploy small changes to production before version bump
**Key Resources:** - **DELEGATE** to the `dual-boot` skill for dual-boot setup with `next_rails` (see Dependencies) - See `references/deprecation-warnings.md` for managing deprecations - See `references/staying-current.md` for maintaining upgrades over time
---
## CRITICAL: Dual-Boot Code Pattern with `NextRails.next?`
When proposing code fixes that must work with both the current and target Rails versions (dual-boot), **always use `NextRails.next?` from the `next_rails` gem** — never use `respond_to?` or other feature-detection patterns.
**DELEGATE** to the `dual-boot` skill for: - Setup and initialization (`next_rails --init`, `Gemfile.next`) - `NextRails.next?` code patterns and examples - CI configuration for dual-boot testing - Post-upgrade cleanup (removing dual-boot branches)
**DEPENDENCY:** Requires the [dual-boot skill](https://github.com/ombulabs/claude-code_dual-boot-skill)
---
## Trigger Patterns
Claude should activate this skill when user says:
**Upgrade Requests:** - "Upgrade my Rails app to [version]" - "Help me upgrade from Rails [x] to [y]" - "What breaking changes are in Rails [version]?" - "Plan my upgrade from [x] to [y]" - "What Rails version am I using?" - "Analyze my Rails app for upgrade" - "Find breaking changes in my code" - "Check my app for Rails [version] compatibility"
**Specific Report Requests:** - "Show me the app:update changes" - "Preview configuration changes for Rails [version]" - "Generate the upgrade report" - "What will change if I upgrade?"
**Upgrade Cleanup Requests (delegate to the `upgrade-cleanup` plugin):** - "Finish the upgrade" - "Clean up after my Rails upgrade" - "Remove the dual-boot setup" - "Drop the NextRails branches" - "We're done upgrading to Rails [version]"
---
## CRITICAL: Sequential Upgrade Strategy
### ⚠️ Version Skipping is NOT Allowed
Rails upgrades MUST follow a sequential path. Examples:
**For Rails 5.x to 8.x:** ``` 5.0.x → 5.1.x → 5.2.x → 6.0.x → 6.1.x → 7.0.x → 7.1.x → 7.2.x → 8.0.x → 8.1.x ```
**You CANNOT skip versions.** Examples: - ❌ 5.2 → 6.1 (skips 6.0) - ❌ 6.0 → 7.0 (skips 6.1) - ❌ 7.0 → 8.0 (skips 7.1 and 7.2) - ✅ 5.2 → 6.0 (correct) - ✅ 7.0 → 7.1 (correct) - ✅ 7.2 → 8.0 (correct)
If user requests a multi-hop upgrade (e.g., 5.2 → 8.1): 1. Explain the sequential requirement 2. Break it into individual hops 3. Generate separate reports for each hop 4. Recommend completing each hop fully before moving to next
---
## Supported Upgrade Paths
### Legacy Rails (2.3 - 4.2)
| From | To | Difficulty | Key Changes | Ruby Required | |------|-----|-----------|-------------|---------------| | 2.3.x | 3.0.x | Very Hard | XSS protection, routes syntax | 1.8.7 - 1.9.3 | | 3.0.x | 3.1.x | Medium | Asset pipeline, jQuery | 1.8.7 - 1.9.3 | | 3.1.x | 3.2.x | Easy | Ruby 1.9.3 support | 1.8.7 - 2.0 | | 3.2.x | 4.0.x | Hard | Strong Parameters, Turbolinks | 1.9.3+ | | 4.0.x | 4.1.x | Medium | Spring, secrets.yml | 1.9.3+ | | 4.1.x | 4.2.x | Medium | ActiveJob, Web Console | 1.9.3+ | | 4.2.x | 5.0.x | Hard | ActionCable, API mode, ApplicationRecord | 2.2.2+ |
### Modern Rails (5.0 - 8.1)
| From | To | Difficulty | Key Changes | Ruby Required | |------|-----|-----------|-------------|---------------| | 5.0.x | 5.1.x | Easy | Encrypted secrets, yarn default | 2.2.2+ | | 5.1.x | 5.2.x | Medium | Active Storage, credentials | 2.2.2+ | | 5.2.x | 6.0.x | Hard | Zeitwerk, Action Mailbox/Text | 2.5.0+ | | 6.0.x | 6.1.x | Medium | Horizontal sharding, strict loading | 2.5.0+ | | 6.1.x | 7.0.x | Hard | Hotwire/Turbo, Import Maps | 2.7.0+ | | 7.0.x | 7.1.x | Medium | Composite keys, async queries | 2.7.0+ | | 7.1.x | 7.2.x | Medium | Transaction-aware jobs, DevContainers | 3.1.0+ | | 7.2.x | 8.0.x | Very Hard | Propshaft, Solid gems, Kamal | 3.2.0+ | | 8.0.x | 8.1.x | Easy | Bundler-audit, max_connections | 3.2.0+ |
---
## Available Resources
### Core Documentation - `SKILL.md` - This file (entry point)
### Version-Specific Guides (Load as needed)
**Legacy Rails:** - `version-guides/upgrade-3.2-to-4.0.md` - Rails 3.2 → 4.0 (Strong Parameters) - `version-guides/upgrade-4.0-to-4.1.md` - Rails 4.0 → 4.1 (Spring, secrets.yml, enums) - `version-guides/upgrade-4.1-to-4.2.md` - Rails 4.1 → 4.2 (ActiveJob, Web Console) - `version-guides/upgrade-4.2-to-5.0.md` - Rails 4.2 → 5.0 (ApplicationRecord)
**Modern Rails:** - `version-guides/upgrade-5.0-to-5.1.md` - Rails 5.0 → 5.1 (Encrypted secrets) - `version-guides/upgrade-5.1-to-5.2.md` - Rails 5.1 → 5.2 (Active Storage, Credentials) - `version-guides/upgrade-5.2-to-6.0.md` - Rails 5.2 → 6.0 (Zeitwerk) - `version-guides/upgrade-6.0-to-6.1.md` - Rails 6.0 → 6.1 (Horizontal sharding) - `version-guides/upgrade-6.1-to-7.0.md` - Rails 6.1 → 7.0 (Hotwire/Turbo) - `version-guides/upgrade-7.0-to-7.1.md` - Rails 7.0 → 7.1 (Composite keys) - `version-guides/upgrade-7.1-to-7.2.md` - Rails 7.1 → 7.2 (Transaction jobs) - `version-guides/upgrade-7.2-to-8.0.md` - Rails 7.2 → 8.0 (Propshaft) - `version-guides/upgrade-8.0-to-8.1.md` - Rails 8.0 → 8.1 (bundler-audit)
### Workflow Guides (Load when generating deliverables) - `workflows/test-suite-verification-workflow.md` - **MANDATORY FIRST STEP** - How to run and verify test suite - `workflows/no-test-suite-smoke-workflow.md` - **Load from Step 1 when no runnable RSpec/Minitest suite exists** - Rails boot, routes, migration-status, and build smoke baseline with partial-confidence reporting - `workflows/direct-detection-workflow.md` - How to run breaking change detection directly - `workflows/upgrade-report-workflow.md` - How to generate upgrade reports - `workflows/gem-compatibility-workflow.md` - **Load in Step 4.5** - Per-lockfile gem compatibility check against the target Rails version. Documents both the primary (`next_rails` `bundle_report compatibility`) and the secondary (railsbump.org API) and the rules for when to escalate. - `workflows/boot-smoke-test-workflow.md` - **Load in Step 4.6** - Run a Rails-loading command against `Gemfile.next` to catch gem-level runtime incompat that the resolver can't see (gems calling removed Rails internals or `require`-ing removed files). - `workflows/ci-sync-workflow.md` - **MANDATORY before opening the upgrade PR** - How to verify CI config matches the upgraded Gemfile - `workflows/app-update-preview-workflow.md` - How to generate app:update previews - **`upgrade-cleanup` companion plugin** - User-triggered. Removes dual-boot scaffolding and drops `NextRails.next?` / `NextRails.current?` branches. Deprecation triage stays with this skill for the next hop.
### Examples (Load when user needs clarification) - `examples/simple-upgrade.md` - Single-hop upgrade example - `examples/multi-hop-upgrade.md` - Multi-hop upgrade example
### External Dependencies - **dual-boot skill** - Dual-boot setup and management with next_rails (Step 2) (https://github.com/ombulabs/claude-code_dual-boot-skill) - **rails-load-defaults skill** - Incremental load_defaults alignment (Step 7, final step) (https://github.com/ombulabs/claude-code_rails-load-defaults-skill)
### Reference Materials - `references/deprecation-warnings.md` - Finding and fixing deprecations - `references/staying-current.md` - Keeping up with Rails releases - `references/breaking-changes-by-version.md` - Quick lookup - `references/multi-hop-strategy.md` - Multi-version planning - `references/testing-checklist.md` - Comprehensive testing - `references/gem-compatibility.md` - Gem update order and the "no compatible version" playbook (fork / vendor / replace). Load only when Step 4.5's compatibility check produced blockers. - `references/js-compressor-sprockets-mismatch.md` - Keeping terser / closure-compiler working when the target Rails pins Sprockets to the 2.x line. Load only when JS_COMPRESSOR_GEM_MISMATCH fires.
### Detection Pattern Resources - `detection-scripts/patterns/rails-*.yml` - Version-specific patterns for direct detection
### Report Templates - `templates/upgrade-report-template.md` - Main upgrade report structure - `templates/app-update-preview-template.md` - Configuration preview
---
## High-Level Workflow
When user requests an upgrade, follow this workflow:
### Step 0: Verify Latest Patch Version (MANDATORY PRE-STEP) ``` ⚠️ THIS STEP IS REQUIRED BEFORE ANY OTHER WORK
1. Read Gemfile.lock to find exact current Rails version (e.g., 3.2.19) 2. Compare against latest patch for that series: - EOL series (≤ 7.1): use static table in references/multi-hop-strategy.md - Active series (≥ 7.2): query RubyGems API (see references/multi-hop-strategy.md for commands) 3. If current version < latest patch: - INFORM user: "Your app is on Rails X.Y.Z but the latest patch is X.Y.W" - Guide through Gemfile update and bundle update rails - Run test suite after patch upgrade - Deploy patch upgrade before proceeding - Do NOT proceed to next minor/major until on latest patch 4. If current version == latest patch: - Proceed to Step 1 ```
**Why patch first:** Patch releases contain security fixes, bug fixes, and additional deprecation warnings. Starting the version hop on the latest patch is safer (the security fixes are already in production) and easier to debug (the new deprecation warnings surface issues that would otherwise show up mid-upgrade).
### Step 1: Run Test Suite (MANDATORY FIRST STEP) ``` ⚠️ THIS STEP IS REQUIRED BEFORE ANY OTHER WORK
1. Read: workflows/test-suite-verification-workflow.md 2. Detect test framework (RSpec, Minitest, or both) 3. Run test suite with: bundle exec rspec OR bundle exec rails test 4. Capture results: total tests, passing, failing, pending 5. If no runnable test suite exists: - Load: work
Source provenance
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for rails-upgrade, ready for a manual X post.
rails-upgrade: Analyzes Rails applications and generates comprehensive upgrade reports with breaking changes... 381 stars https://www.openagentskill.com/skills/ombulabs-rails-upgrade?ref=x
Listing + install path for rails-upgrade: https://www.openagentskill.com/skills/ombulabs-rails-upgrade?ref=x Install: npx skills add ombulabs/claude-code_rails-upgrade-skill --skill rails-upgrade
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to ombulabs but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/ombulabs-rails-upgrade?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/ombulabs-rails-upgrade?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/ombulabs-rails-upgrade/audit)
[](https://www.openagentskill.com/skills/ombulabs-rails-upgrade?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)ombulabs
@ombulabs
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Do not auto-install
mono-color
Generate original one-ink or controlled two-ink editorial images from any theme, sentence, article idea, object, or reference photo. Always use this skill when the user asks for 单色海报、双色印刷、单色调视觉、蓝色/绿色孔版印刷、risograph、网点照片、复古或当代编辑排版、zine poster, monochrome editorial poster, duotone print, or asks to use the mono-color style. It uses an adaptive white, gray, or pale-beige substrate, no more than two printing inks, active negative space, terse human language, and strong serif/grotesk/mono typography without making retro styling the default or copying a source composition, wording, logo, or artwork. Produce both the final generation prompt and the generated raster image unless the user explicitly asks for prompt only.
1.9K StarsLast30days Skill
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
61.0K StarsAcademic Research Skills
Academic Research Skills for Claude Code: research → write → review → revise → finalize
38.4K Starsgrill-me
A relentless interview to sharpen a plan or design.
256.3K StarsPermission surface
shell or command execution, filesystem or document access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
shell or command execution, filesystem or document access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
shell or command execution, filesystem or document access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
shell or command execution, filesystem or document access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness