Presented at Artificial Ruby NYC on March 25th, 2026.
For more than 8 years, we've been upgrading Rails applications at FastRuby.io. More than 60,000 developer-hours going from Rails 2.3 all the way to 8.1. Along the way, we've learned what
works and what doesn't — and we've seen what happens when teams skip versions or ignore deprecation warnings.
Claude Code is great at general coding tasks, but on its own, it doesn't know that dual booting is worth the effort. It doesn't know that you should address deprecation warnings before you
upgrade. It doesn't know that your load_defaults should match your version of Rails. Without that structure, even the most capable AI will take shortcuts that create problems down the road.
So we encoded our methodology into three open-source Claude Code skills:
- Rails Upgrade Skill — enforces sequential upgrades and generates codebase-specific migration reports: https://github.com/ombulabs/claude-code_rails-upgrade-skill
- Dual Boot Skill — sets up next_rails so you can run your test suite against both Rails versions locally, in CI, and eventually in production:
https://github.com/ombulabs/claude-code_dual-boot-skill
- Rails Load Defaults Skill — walks through each new_framework_defaults config one at a time until your load_defaults matches your Rails version:
https://github.com/ombulabs/claude-code_rails-load-defaults-skill
In this talk I cover why generic AI falls short for complex upgrades, the opinionated decisions we baked into each skill, and then I do a live demo showing how the three skills work
together.
If you want to give it a try: https://github.com/ombulabs/claude-code_rails-upgrade-skill
Blog post with more details: https://www.fastruby.io/blog/open-source-claude-code-skill-for-rails-upgrades.html