claude-code_rails-upgrade-skill

왜 쓰나요

핵심 기능

Version-aware playbooks (Rails 6 → 7, 7 → 7.1, 7.1 → 7.2, 7.2 → 8)
Deprecation warning sweep + fix suggestions
Framework defaults migration (rails app:update)
Gem compatibility checks against target Rails version
Spring cleaning (Spring removal in newer Rails)
Test-first upgrade: fix tests before cutover

라이브 데모

실제 사용 모습

claude-code-rails-upgrade-skill.replay ▶ 준비됨

0/0

설치

작성자 저장소 · Claude Skills 공식 문서

사용 사례

실전 활용법: claude-code_rails-upgrade-skill

How to plan a Rails upgrade before touching code

👤 Rails devs facing a multi-version jump ⏱ ~60 min intermediate

언제 쓸까: You're on Rails 6.1 and need to get to 7.2. You want a plan, not a prayer.

흐름

Audit current state

Audit this Rails app: current version, Ruby version, gems, deprecation warnings from a test run.✓ 복사됨

→ Baseline report
Build the path

Plan the upgrade to Rails 7.2. Go version-by-version (6.1 → 7.0 → 7.1 → 7.2), each with milestone criteria.✓ 복사됨

→ Multi-stage plan
Identify blockers

Which gems don't have a 7.2-compatible version? Proposals for each (upgrade/replace/fork).✓ 복사됨

→ Per-gem blocker list

결과: A realistic upgrade plan with staged milestones.

함정

Jumping two major versions at once — Skill enforces one minor/major at a time — don't override

Sweep and fix deprecation warnings

👤 Rails devs mid-upgrade ⏱ ~90 min intermediate

언제 쓸까: You're between versions and the test run is a wall of deprecation warnings.

흐름

Collect

Run tests, collect all unique deprecation warnings.✓ 복사됨

→ Deduped list with file:line occurrences
Group + fix

Group by cause. Propose minimal fixes with diffs for each group.✓ 복사됨

→ Grouped fix diffs

결과: A clean test run ready for the next version bump.

Apply new framework defaults safely

👤 Rails devs navigating rails app:update ⏱ ~60 min advanced

언제 쓸까: You've bumped the Gemfile and ran rails app:update; now you have a bunch of new initializers.

흐름

Review diff

Review the diff from rails app:update. Flag any default change that could break our app (strict_loading, zeitwerk mode, etc.).✓ 복사됨

→ Per-change risk annotation
Staged enable

For each risky default, produce a staged rollout: enable behind env flag, validate on staging, then flip.✓ 복사됨

→ Staged plan per default

결과: Defaults enabled without surprise regressions.

함정

Enabling all load_defaults at once — Use new_framework_defaults_X.Y.rb to ramp individually

조합

다른 MCP와 조합해 10배 효율

claude-code-rails-upgrade-skill + claude-code-owasp-skill

Security review on the upgraded code

After upgrade to Rails 7.2, run OWASP review on the auth and params handling.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출	비용
Audit	repo	Start of every upgrade	Claude tokens
Plan upgrade path	current, target	After audit	Claude tokens
Gem compat check	Gemfile, target Rails	Before bumping	Claude tokens + RubyGems API
Deprecation sweep	test log	Between versions	Claude tokens
Framework defaults migration	diff from rails app:update	After rails app:update	Claude tokens

비용 및 제한

운영 비용

API 쿼터: None
호출당 토큰: 20-80k across an upgrade
금액: Free
팁: Run deprecation sweeps on specific directories rather than the whole app at once.

보안

권한, 시크릿, 파급범위

자격 증명 저장: No credentials

데이터 외부 송신: Code sent to Claude for inference

Always upgrade on a branch. Don't let Claude run destructive commands (db:migrate, bundle update) without explicit confirmation.

문제 해결

자주 발생하는 오류와 해결

rails app:update produces uncommitted binary files

These are usually system files. Gitignore them and regenerate cleanly.

Tests pass locally, fail in CI after upgrade

Likely autoloading differences or eager_load in production mode. Run with RAILS_ENV=production locally.

Gem bundle resolution fails

Skill will suggest alternative gem versions; sometimes a fork or replacement is required.

확인: bundle update --conservative

대안