Skip to content

ombulabs/claude-code_rails-upgrade-skill / rails-upgrade

rails-upgrade

Verified

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, querying version-specific changes, or answering what stands between the app and the next Rails version. Based on FastRuby.io methodology and "The Complete Guide to Upgrade Rails" ebook.

FileKindSize
SKILL.mdskill md11.0 KB
detection-scripts/gem_limits.rbscript6.0 KB
detection-scripts/hop.rbscript2.2 KB
detection-scripts/patterns/rails-40-patterns.expectations.ymlconfig43.8 KB
detection-scripts/patterns/rails-40-patterns.ymlconfig96.5 KB
detection-scripts/patterns/rails-41-patterns.expectations.ymlconfig25.6 KB
detection-scripts/patterns/rails-41-patterns.ymlconfig59.8 KB
detection-scripts/patterns/rails-42-patterns.expectations.ymlconfig27.5 KB
detection-scripts/patterns/rails-42-patterns.ymlconfig48.7 KB
detection-scripts/patterns/rails-50-patterns.expectations.ymlconfig1.9 KB
detection-scripts/patterns/rails-50-patterns.ymlconfig8.1 KB
detection-scripts/patterns/rails-51-patterns.expectations.ymlconfig4.2 KB
detection-scripts/patterns/rails-51-patterns.ymlconfig15.0 KB
detection-scripts/patterns/rails-52-patterns.expectations.ymlconfig5.0 KB
detection-scripts/patterns/rails-52-patterns.ymlconfig14.7 KB
detection-scripts/patterns/rails-60-patterns.expectations.ymlconfig1007 B
detection-scripts/patterns/rails-60-patterns.ymlconfig14.2 KB
detection-scripts/patterns/rails-70-patterns.expectations.ymlconfig4.0 KB
detection-scripts/patterns/rails-70-patterns.ymlconfig11.2 KB
detection-scripts/patterns/rails-71-patterns.expectations.ymlconfig3.1 KB
detection-scripts/patterns/rails-71-patterns.ymlconfig9.5 KB
detection-scripts/patterns/rails-72-patterns.expectations.ymlconfig1.2 KB
detection-scripts/patterns/rails-72-patterns.ymlconfig6.1 KB
detection-scripts/patterns/rails-80-patterns.expectations.ymlconfig6.6 KB
detection-scripts/patterns/rails-80-patterns.ymlconfig21.2 KB
detection-scripts/patterns/rails-81-patterns.expectations.ymlconfig4.3 KB
detection-scripts/patterns/rails-81-patterns.ymlconfig13.2 KB
detection-scripts/scan_patterns.rbscript42.8 KB
examples/multi-hop-upgrade.mdmarkdown18.9 KB
examples/simple-upgrade.mdmarkdown4.0 KB
references/breaking-changes-by-version-reference.mdmarkdown3.9 KB
references/deprecation-warnings-reference.mdmarkdown10.7 KB
references/gem-compatibility-reference.mdmarkdown8.2 KB
references/js-compressor-sprockets-mismatch-reference.mdmarkdown4.7 KB
references/multi-hop-strategy-reference.mdmarkdown8.8 KB
references/next-hop-readiness-reference.mdmarkdown2.1 KB
references/no-test-suite-smoke-reference.mdmarkdown4.7 KB
references/request-patterns-reference.mdmarkdown3.7 KB
references/sequential-strategy-reference.mdmarkdown2.1 KB
references/staying-current-reference.mdmarkdown7.8 KB
references/testing-checklist-reference.mdmarkdown6.3 KB
templates/app-update-preview-template.mdmarkdown4.3 KB
templates/upgrade-report-template.mdmarkdown10.2 KB
version-guides/upgrade-3.2-to-4.0.mdmarkdown68.0 KB
version-guides/upgrade-4.0-to-4.1.mdmarkdown66.7 KB
version-guides/upgrade-4.1-to-4.2.mdmarkdown60.7 KB
version-guides/upgrade-4.2-to-5.0.mdmarkdown9.7 KB
version-guides/upgrade-5.0-to-5.1.mdmarkdown19.1 KB
version-guides/upgrade-5.1-to-5.2.mdmarkdown17.7 KB
version-guides/upgrade-5.2-to-6.0.mdmarkdown6.4 KB
version-guides/upgrade-6.0-to-6.1.mdmarkdown6.8 KB
version-guides/upgrade-6.1-to-7.0.mdmarkdown14.7 KB
version-guides/upgrade-7.0-to-7.1.mdmarkdown13.2 KB
version-guides/upgrade-7.1-to-7.2.mdmarkdown11.2 KB
version-guides/upgrade-7.2-to-8.0.mdmarkdown23.1 KB
version-guides/upgrade-8.0-to-8.1.mdmarkdown14.0 KB
workflows/00-verify-latest-patch-workflow.mdmarkdown1.7 KB
workflows/01-run-test-suite-workflow.mdmarkdown12.7 KB
workflows/02-resolve-deprecation-warnings-workflow.mdmarkdown6.3 KB
workflows/03-validate-upgrade-path-workflow.mdmarkdown1.8 KB
workflows/04-setup-next-rails-workflow.mdmarkdown1.5 KB
workflows/05-detect-breaking-changes-workflow.mdmarkdown20.0 KB
workflows/06-check-gem-compatibility-workflow.mdmarkdown11.1 KB
workflows/07-boot-smoke-test-workflow.mdmarkdown7.3 KB
workflows/08-generate-upgrade-report-workflow.mdmarkdown12.7 KB
workflows/09-generate-app-update-preview-workflow.mdmarkdown7.3 KB
workflows/10-implement-and-upgrade-workflow.mdmarkdown2.5 KB
workflows/11-sync-ci-workflow.mdmarkdown8.6 KB
workflows/12-align-load-defaults-workflow.mdmarkdown952 B
workflows/13-mention-cleanup-workflow.mdmarkdown1.3 KB

references/staying-current-reference.md

View on GitHub
# Staying Current with Rails

**Based on "The Complete Guide to Upgrade Rails" by FastRuby.io (OmbuLabs)**

---

## Overview

Congratulations on completing your Rails upgrade! Now the goal is to never fall behind again. This guide covers strategies to keep your Rails application current.

---

## Continuous Integration with Dual-Boot

Set up your CI to run tests against both your current Rails version and the next version. This way you're always prepared for the next upgrade.

### CircleCI Configuration

```yaml
# .circleci/config.yml

version: 2.1

jobs:
  build-current:
    docker:
      - image: cimg/ruby:3.2.0
        environment:
          RAILS_ENV: test
          DATABASE_URL: postgres://postgres@localhost/myapp_test
      - image: cimg/postgres:14.0
    steps:
      - checkout
      - run: bundle install
      - run: bundle exec rails db:create db:schema:load
      - run: bundle exec rspec

  build-next:
    docker:
      - image: cimg/ruby:3.2.0
        environment:
          RAILS_ENV: test
          DATABASE_URL: postgres://postgres@localhost/myapp_test
          BUNDLE_GEMFILE: Gemfile.next
      - image: cimg/postgres:14.0
    steps:
      - checkout
      - run: bundle install
      - run: bundle exec rails db:create db:schema:load
      - run: bundle exec rspec

workflows:
  version: 2
  test:
    jobs:
      - build-current
      - build-next:
          # Run next version tests, but don't block deploys
          requires:
            - build-current
```

### Travis CI Configuration

```yaml
# .travis.yml

language: ruby
cache: bundler

rvm:
  - 3.2.0

gemfile:
  - Gemfile
  - Gemfile.next

services:
  - postgresql

before_script:
  - bundle install
  - bundle exec rails db:create db:schema:load

script:
  - bundle exec rspec

# Allow next version failures (informational only)
jobs:
  allow_failures:
    - gemfile: Gemfile.next
```

### GitHub Actions Configuration

```yaml
# .github/workflows/ci.yml

name: CI

on: [push, pull_request]

jobs:
  test-current:
    runs-on: ubuntu-latest
    env:
      RAILS_ENV: test
      DATABASE_URL: postgres://postgres:postgres@localhost/myapp_test

    services:
      postgres:
        image: postgres:14
        env:
          POSTGRES_PASSWORD: postgres
        ports:
          - 5432:5432

    steps:
      - uses: actions/checkout@v3
      - uses: ruby/setup-ruby@v1
        with:
          ruby-version: 3.2
          bundler-cache: true
      - run: bundle exec rails db:create db:schema:load
      - run: bundle exec rspec

  test-next:
    runs-on: ubuntu-latest
    continue-on-error: true  # Don't block PR merges
    env:
      RAILS_ENV: test
      DATABASE_URL: postgres://postgres:postgres@localhost/myapp_test
      BUNDLE_GEMFILE: Gemfile.next

    services:
      postgres:
        image: postgres:14
        env:
          POSTGRES_PASSWORD: postgres
        ports:
          - 5432:5432

    steps:
      - uses: actions/checkout@v3
      - uses: ruby/setup-ruby@v1
        with:
          ruby-version: 3.2
          bundler-cache: true
      - run: bundle exec rails db:create db:schema:load
      - run: bundle exec rspec
```

---

## Tracking Outdated Dependencies

### Regular Dependency Audits

Schedule regular checks for outdated gems:

```bash
# Check all outdated gems
bundle outdated

# Check only direct dependencies
bundle outdated --only-explicit

# Check for security vulnerabilities
bundle audit check --update
```

### Automated Dependency Updates

Use tools like [Dependabot](https://docs.github.com/en/code-security/dependabot) or [Renovate](https://www.mend.io/renovate/) to automatically create PRs for dependency updates.

**Dependabot configuration:**

```yaml
# .github/dependabot.yml

version: 2
updates:
  - package-ecosystem: "bundler"
    directory: "/"
    schedule:
      interval: "weekly"
    open-pull-requests-limit: 5
    groups:
      rails:
        patterns:
          - "rails"
          - "actioncable"
          - "actionmailer"
          - "actionpack"
          - "actionview"
          - "activejob"
          - "activemodel"
          - "activerecord"
          - "activestorage"
          - "activesupport"
          - "railties"
```

### Test-Driven Updates

Create a workflow where every dependency update:

1. Creates a pull request
2. Runs the full test suite
3. Requires code review
4. Gets deployed to staging
5. QA verification
6. Production deployment

---

## Testing Against Rails Master

Stay ahead of releases by testing against Rails' main branch:

### Gemfile Configuration

```ruby
# Gemfile

def next?
  File.basename(__FILE__) == "Gemfile.next"
end

if next?
  # Test against Rails main branch
  gem 'rails', github: 'rails/rails', branch: 'main'
else
  gem 'rails', '~> 7.1.0'
end
```

### When to Test Against Main

- **Weekly**: Run CI against Rails main once a week
- **Before major releases**: Increase frequency before new Rails versions
- **After RC releases**: Test release candidates immediately

### Benefits

- Discover breaking changes early
- Contribute fixes to Rails
- Be ready on release day
- Understand upcoming features

---

## Release Monitoring

### Stay Informed

1. **Rails Blog**: https://rubyonrails.org/blog/
2. **Rails Twitter**: https://twitter.com/rails
3. **Rails GitHub Releases**: https://github.com/rails/rails/releases
4. **Ruby Weekly Newsletter**: https://rubyweekly.com/

### Version Monitoring Tools

```ruby
# Add to Gemfile
gem 'libyear-bundler', group: :development
```

```bash
# Check how "out of date" your dependencies are
bundle libyear
```

---

## Upgrade Schedule

### Recommended Cadence

| Cycle | Action |
|-------|--------|
| Weekly | Check `bundle outdated` |
| Monthly | Update patch versions |
| Quarterly | Update minor versions |
| Annually | Plan major version upgrade |

### When to Upgrade

**Upgrade immediately:**
- Security patches (x.y.Z releases)
- Critical bug fixes

**Upgrade soon (within 1-2 months):**
- Minor versions with important features
- Dependency requirements

**Plan for next quarter:**
- Major version upgrades
- Breaking changes

---

## Team Practices

### Ownership

Assign ownership for keeping dependencies current:

- **Rails version**: Senior developer or tech lead
- **Security gems**: Security-conscious team member
- **CI/CD tools**: DevOps or platform team

### Documentation

Maintain upgrade documentation:

- Record decisions made during upgrades
- Note workarounds for specific issues
- Track gems that commonly cause problems
- Document custom patches or forks

### Knowledge Sharing

After each upgrade:

- Hold a brief retrospective
- Share learnings with the team
- Update internal documentation
- Consider blog posts or conference talks

---

## Preventive Measures

### Don't Accumulate Debt

1. **Address deprecations immediately** - Don't let them pile up
2. **Update gems regularly** - Small updates are easier than big jumps
3. **Keep test coverage high** - Makes upgrades safe
4. **Review changelogs** - Understand what's changing

### Avoid Common Traps

- **Don't pin to old versions** without a plan to upgrade
- **Don't ignore CI warnings** about deprecated features
- **Don't skip testing** to save time
- **Don't deploy untested upgrades** directly to production

---

## Quick Reference

### Commands

```bash
# Check outdated gems
bundle outdated

# Security audit
bundle audit check --update

# Update a specific gem
bundle update gem_name --conservative

# Update all gems (careful!)
bundle update
```

### CI Environment Variables

```bash
# Run with next Rails version
BUNDLE_GEMFILE=Gemfile.next bundle exec rspec

# Enable deprecation warnings
RUBYOPT="-W:deprecated" bundle exec rspec
```

---

## Resources

- [RailsBump](https://railsbump.org/) - Gem compatibility checker
- [RailsDiff](https://railsdiff.org/) - Compare Rails versions
- [FastRuby.io Blog](https://www.fastruby.io/blog) - Upgrade guides and tips
- [next_rails gem](https://github.com/fastruby/next_rails) - Dual-boot tool
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall