/ Verzeichnis / Playground / claude-code_rails-upgrade-skill
← Alle Server ↗ GitHub
● Community ombulabs ⚡ Sofort

claude-code_rails-upgrade-skill

von ombulabs · ombulabs/claude-code_rails-upgrade-skill

Claude Code skill that methodically upgrades Rails — from audit through deprecation fixes to bundle update — without breaking everything.

Rails Upgrade Skill (by OmbuLabs) walks Claude through the standard Rails upgrade playbook: audit the codebase, fix deprecations, apply framework defaults, handle gem incompatibilities, and verify on the new version. Based on OmbuLabs' production experience upgrading Rails apps. Good for going N → N+1, or catching up from older versions.

▶ Demo ansehen 📦 Installieren 💡 Anwendungsfälle

Warum nutzen

Hauptfunktionen

Live-Demo

In der Praxis

claude-code-rails-upgrade-skill.replay ▶ bereit
0/0

Installation

Repository des Autors · Offizielle Dokumentation zu Claude Skills

Anwendungsfälle

Praxisnahe Nutzung: claude-code_rails-upgrade-skill

How to plan a Rails upgrade before touching code

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

Wann einsetzen: You're on Rails 6.1 and need to get to 7.2. You want a plan, not a prayer.

Ablauf
  1. Audit current state
    Audit this Rails app: current version, Ruby version, gems, deprecation warnings from a test run.✓ Kopiert
    → Baseline report
  2. 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.✓ Kopiert
    → Multi-stage plan
  3. Identify blockers
    Which gems don't have a 7.2-compatible version? Proposals for each (upgrade/replace/fork).✓ Kopiert
    → Per-gem blocker list

Ergebnis: A realistic upgrade plan with staged milestones.

Fallstricke
  • 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

Wann einsetzen: You're between versions and the test run is a wall of deprecation warnings.

Ablauf
  1. Collect
    Run tests, collect all unique deprecation warnings.✓ Kopiert
    → Deduped list with file:line occurrences
  2. Group + fix
    Group by cause. Propose minimal fixes with diffs for each group.✓ Kopiert
    → Grouped fix diffs

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

Apply new framework defaults safely

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

Wann einsetzen: You've bumped the Gemfile and ran rails app:update; now you have a bunch of new initializers.

Ablauf
  1. Review diff
    Review the diff from rails app:update. Flag any default change that could break our app (strict_loading, zeitwerk mode, etc.).✓ Kopiert
    → Per-change risk annotation
  2. Staged enable
    For each risky default, produce a staged rollout: enable behind env flag, validate on staging, then flip.✓ Kopiert
    → Staged plan per default

Ergebnis: Defaults enabled without surprise regressions.

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

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

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.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

WerkzeugEingabenWann aufrufenKosten
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

Kosten & Limits

Was der Betrieb kostet

API-Kontingent
None
Tokens pro Aufruf
20-80k across an upgrade
Kosten in €
Free
Tipp
Run deprecation sweeps on specific directories rather than the whole app at once.

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: No credentials
Datenabfluss: Code sent to Claude for inference

Fehlerbehebung

Häufige Fehler und Lösungen

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.

Prüfen: bundle update --conservative

Alternativen

claude-code_rails-upgrade-skill vs. andere

AlternativeWann stattdessenKompromiss
next_rails gemYou want a deterministic upgrade helperNo LLM-guided deprecation fixes

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen