claude-code_rails-upgrade-skill MCP — Anwendungsfälle, Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

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

Live-Demo

In der Praxis

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

0/0

Installieren

Wählen Sie Ihren Client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "claude-code-rails-upgrade-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/ombulabs/claude-code_rails-upgrade-skill",
        "~/.claude/skills/claude-code_rails-upgrade-skill"
      ],
      "_inferred": true
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "claude-code-rails-upgrade-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/ombulabs/claude-code_rails-upgrade-skill",
        "~/.claude/skills/claude-code_rails-upgrade-skill"
      ],
      "_inferred": true
    }
  }
}

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "claude-code-rails-upgrade-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/ombulabs/claude-code_rails-upgrade-skill",
        "~/.claude/skills/claude-code_rails-upgrade-skill"
      ],
      "_inferred": true
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "claude-code-rails-upgrade-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/ombulabs/claude-code_rails-upgrade-skill",
        "~/.claude/skills/claude-code_rails-upgrade-skill"
      ],
      "_inferred": true
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "claude-code-rails-upgrade-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/ombulabs/claude-code_rails-upgrade-skill",
        "~/.claude/skills/claude-code_rails-upgrade-skill"
      ]
    }
  ]
}

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

{
  "context_servers": {
    "claude-code-rails-upgrade-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/ombulabs/claude-code_rails-upgrade-skill",
          "~/.claude/skills/claude-code_rails-upgrade-skill"
        ]
      }
    }
  }
}

In context_servers hinzufügen. Zed lädt beim Speichern neu.

claude mcp add claude-code-rails-upgrade-skill -- git clone https://github.com/ombulabs/claude-code_rails-upgrade-skill ~/.claude/skills/claude-code_rails-upgrade-skill

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

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.

Voraussetzungen

Skill installed — git clone https://github.com/ombulabs/claude-code_rails-upgrade-skill ~/.claude/skills/rails-upgrade-skill
Git-clean working tree — Always upgrade on a branch; commit current state

Ablauf

Audit current state

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

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

→ Multi-stage plan
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

Collect

Run tests, collect all unique deprecation warnings.✓ Kopiert

→ Deduped list with file:line occurrences
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

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

Werkzeug	Eingaben	Wann aufrufen	Kosten
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

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

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

Alternative	Wann stattdessen	Kompromiss
next_rails gem	You want a deterministic upgrade helper	No LLM-guided deprecation fixes

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen