Registry に収録
rails-upgrade
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, or querying version-specific changes. Base
概要
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, or querying version-specific changes. Based on FastRuby.io methodology and "The Complete Guide to Upgrade Rails" ebook.
説明全文を読む
ソース文書であり、このサイトへの操作指示ではありません。コマンド実行前に権限を確認してください。
Rails Upgrade Assistant Skill
Skill Identity
- Name: Rails Upgrade Assistant
- Purpose: Intelligent Rails application upgrades from 2.3 through 8.1
- Skill Type: Modular with external workflows and examples
- Upgrade Strategy: Sequential only (no version skipping)
- Methodology: Based on FastRuby.io upgrade best practices and "The Complete Guide to Upgrade Rails" ebook
- Attribution: Content based on "The Complete Guide to Upgrade Rails" by FastRuby.io (OmbuLabs)
Dependencies
- dual-boot skill (github.com/ombulabs/claude-code_dual-boot-skill) — Sets up and manages dual-boot environments using the
next_railsgem. Covers setup,NextRails.next?code patterns, CI configuration, and post-upgrade cleanup. Must be installed for Step 2 of the upgrade workflow. - rails-load-defaults skill (github.com/ombulabs/claude-code_rails-load-defaults-skill) — Handles incremental
load_defaultsupdates with tiered risk assessment (Tier 1: low-risk, Tier 2: needs codebase grep, Tier 3: requires human review). Used as the final step after the Rails version upgrade is complete.
Core Methodology (FastRuby.io Approach)
This skill follows the proven FastRuby.io upgrade methodology:
- Incremental Upgrades - Always upgrade one minor/major version at a time
- Assessment First - Understand scope before making changes
- Dual-Boot Testing - Test both versions during transition using
next_railsgem - Test Coverage - Ensure adequate test coverage before upgrading (aim for 80%+)
- Gem Compatibility - Check gem compatibility at each step using RailsBump
- Deprecation Warnings - Address deprecations before upgrading
- Backwards Compatible Changes - Deploy small changes to production before version bump
Key Resources:
- DELEGATE to the
dual-bootskill for dual-boot setup withnext_rails(see Dependencies) - See
references/deprecation-warnings.mdfor managing deprecations - See
references/staying-current.mdfor maintaining upgrades over time
CRITICAL: Dual-Boot Code Pattern with NextRails.next?
When proposing code fixes that must work with both the current and target Rails versions (dual-boot), always use NextRails.next? from the next_rails gem — never use respond_to? or other feature-detection patterns.
DELEGATE to the dual-boot skill for:
- Setup and initialization (
next_rails --init,Gemfile.next) NextRails.next?code patterns and examples- CI configuration for dual-boot testing
- Post-upgrade cleanup (removing dual-boot branches)
DEPENDENCY: Requires the dual-boot skill
Trigger Patterns
Claude should activate this skill when user says:
Upgrade Requests:
- "Upgrade my Rails app to [version]"
- "Help me upgrade from Rails [x] to [y]"
- "What breaking changes are in Rails [version]?"
- "Plan my upgrade from [x] to [y]"
- "What Rails version am I using?"
- "Analyze my Rails app for upgrade"
- "Find breaking changes in my code"
- "Check my app for Rails [version] compatibility"
Specific Report Requests:
- "Show me the app:update changes"
- "Preview configuration changes for Rails [version]"
- "Generate the upgrade report"
- "What will change if I upgrade?"
Upgrade Cleanup Requests (delegate to the upgrade-cleanup plugin):
- "Finish the upgrade"
- "Clean up after my Rails upgrade"
- "Remove the dual-boot setup"
- "Drop the NextRails branches"
- "We're done upgrading to Rails [version]"
CRITICAL: Sequential Upgrade Strategy
⚠️ Version Skipping is NOT Allowed
Rails upgrades MUST follow a sequential path. Examples:
For Rails 5.x to 8.x:
5.0.x → 5.1.x → 5.2.x → 6.0.x → 6.1.x → 7.0.x → 7.1.x → 7.2.x → 8.0.x → 8.1.x
You CANNOT skip versions. Examples:
- ❌ 5.2 → 6.1 (skips 6.0)
- ❌ 6.0 → 7.0 (skips 6.1)
- ❌ 7.0 → 8.0 (skips 7.1 and 7.2)
- ✅ 5.2 → 6.0 (correct)
- ✅ 7.0 → 7.1 (correct)
- ✅ 7.2 → 8.0 (correct)
If user requests a multi-hop upgrade (e.g., 5.2 → 8.1):
- Explain the sequential requirement
- Break it into individual hops
- Generate separate reports for each hop
- Recommend completing each hop fully before moving to next
Supported Upgrade Paths
Legacy Rails (2.3 - 4.2)
| From | To | Difficulty | Key Changes | Ruby Required |
|---|---|---|---|---|
| 2.3.x | 3.0.x | Very Hard | XSS protection, routes syntax | 1.8.7 - 1.9.3 |
| 3.0.x | 3.1.x | Medium | Asset pipeline, jQuery | 1.8.7 - 1.9.3 |
| 3.1.x | 3.2.x | Easy | Ruby 1.9.3 support | 1.8.7 - 2.0 |
| 3.2.x | 4.0.x | Hard | Strong Parameters, Turbolinks | 1.9.3+ |
| 4.0.x | 4.1.x | Medium | Spring, secrets.yml | 1.9.3+ |
| 4.1.x | 4.2.x | Medium | ActiveJob, Web Console | 1.9.3+ |
| 4.2.x | 5.0.x | Hard | ActionCable, API mode, ApplicationRecord | 2.2.2+ |
Modern Rails (5.0 - 8.1)
| From | To | Difficulty | Key Changes | Ruby Required |
|---|---|---|---|---|
| 5.0.x | 5.1.x | Easy | Encrypted secrets, yarn default | 2.2.2+ |
| 5.1.x | 5.2.x | Medium | Active Storage, credentials | 2.2.2+ |
| 5.2.x | 6.0.x | Hard | Zeitwerk, Action Mailbox/Text | 2.5.0+ |
| 6.0.x | 6.1.x | Medium | Horizontal sharding, strict loading | 2.5.0+ |
| 6.1.x | 7.0.x | Hard | Hotwire/Turbo, Import Maps | 2.7.0+ |
| 7.0.x | 7.1.x | Medium | Composite keys, async queries | 2.7.0+ |
| 7.1.x | 7.2.x | Medium | Transaction-aware jobs, DevContainers | 3.1.0+ |
| 7.2.x | 8.0.x | Very Hard | Propshaft, Solid gems, Kamal | 3.2.0+ |
| 8.0.x | 8.1.x | Easy | Bundler-audit, max_connections | 3.2.0+ |
Available Resources
Core Documentation
SKILL.md- This file (entry point)
Version-Specific Guides (Load as needed)
Legacy Rails:
version-guides/upgrade-3.2-to-4.0.md- Rails 3.2 → 4.0 (Strong Parameters)version-guides/upgrade-4.0-to-4.1.md- Rails 4.0 → 4.1 (Spring, secrets.yml, enums)version-guides/upgrade-4.1-to-4.2.md- Rails 4.1 → 4.2 (ActiveJob, Web Console)version-guides/upgrade-4.2-to-5.0.md- Rails 4.2 → 5.0 (ApplicationRecord)
Modern Rails:
version-guides/upgrade-5.0-to-5.1.md- Rails 5.0 → 5.1 (Encrypted secrets)version-guides/upgrade-5.1-to-5.2.md- Rails 5.1 → 5.2 (Active Storage, Credentials)version-guides/upgrade-5.2-to-6.0.md- Rails 5.2 → 6.0 (Zeitwerk)version-guides/upgrade-6.0-to-6.1.md- Rails 6.0 → 6.1 (Horizontal sharding)version-guides/upgrade-6.1-to-7.0.md- Rails 6.1 → 7.0 (Hotwire/Turbo)version-guides/upgrade-7.0-to-7.1.md- Rails 7.0 → 7.1 (Composite keys)version-guides/upgrade-7.1-to-7.2.md- Rails 7.1 → 7.2 (Transaction jobs)version-guides/upgrade-7.2-to-8.0.md- Rails 7.2 → 8.0 (Propshaft)version-guides/upgrade-8.0-to-8.1.md- Rails 8.0 → 8.1 (bundler-audit)
Workflow Guides (Load when generating deliverables)
workflows/test-suite-verification-workflow.md- MANDATORY FIRST STEP - How to run and verify test suiteworkflows/no-test-suite-smoke-workflow.md- Load from Step 1 when no runnable RSpec/Minitest suite exists - Rails boot, routes, migration-status, and build smoke baseline with partial-confidence reportingworkflows/direct-detection-workflow.md- How to run breaking change detection directlyworkflows/upgrade-report-workflow.md- How to generate upgrade reportsworkflows/gem-compatibility-workflow.md- Load in Step 4.5 - Per-lockfile gem compatibility check against the target Rails version. Documents both the primary (next_railsbundle_report compatibility) and the secondary (railsbump.org API) and the rules for when to escalate.workflows/boot-smoke-test-workflow.md- Load in Step 4.6 - Run a Rails-loading command againstGemfile.nextto catch gem-level runtime incompat that the resolver can't see (gems calling removed Rails internals orrequire-ing removed files).workflows/ci-sync-workflow.md- MANDATORY before opening the upgrade PR - How to verify CI config matches the upgraded Gemfileworkflows/app-update-preview-workflow.md- How to generate app:update previewsupgrade-cleanupcompanion plugin - User-triggered. Removes dual-boot scaffolding and dropsNextRails.next?/NextRails.current?branches. Deprecation triage stays with this skill for the next hop.
Examples (Load when user needs clarification)
examples/simple-upgrade.md- Single-hop upgrade exampleexamples/multi-hop-upgrade.md- Multi-hop upgrade example
External Dependencies
- dual-boot skill - Dual-boot setup and management with next_rails (Step 2) (https://github.com/ombulabs/claude-code_dual-boot-skill)
- rails-load-defaults skill - Incremental load_defaults alignment (Step 7, final step) (https://github.com/ombulabs/claude-code_rails-load-defaults-skill)
Reference Materials
references/deprecation-warnings.md- Finding and fixing deprecationsreferences/staying-current.md- Keeping up with Rails releasesreferences/breaking-changes-by-version.md- Quick lookupreferences/multi-hop-strategy.md- Multi-version planningreferences/testing-checklist.md- Comprehensive testingreferences/gem-compatibility.md- Gem update order and the "no compatible version" playbook (fork / vendor / replace). Load only when Step 4.5's compatibility check produced blockers.references/js-compressor-sprockets-mismatch.md- Keeping terser / closure-compiler working when the target Rails pins Sprockets to the 2.x line. Load only when JS_COMPRESSOR_GEM_MISMATCH fires.
Detection Pattern Resources
detection-scripts/patterns/rails-*.yml- Version-specific patterns for direct detection
Report Templates
templates/upgrade-report-template.md- Main upgrade report structuretemplates/app-update-preview-template.md- Configuration preview
High-Level Workflow
When user requests an upgrade, follow this workflow:
Step 0: Verify Latest Patch Version (MANDATORY PRE-STEP)
⚠️ THIS STEP IS REQUIRED BEFORE ANY OTHER WORK
1. Read Gemfile.lock to find exact current Rails version (e.g., 3.2.19)
2. Compare against latest patch for that series:
- EOL series (≤ 7.1): use static table in references/multi-hop-strategy.md
- Active series (≥ 7.2): query RubyGems API (see references/multi-hop-strategy.md for commands)
3. If current version < latest patch:
- INFORM user: "Your app is on Rails X.Y.Z but the latest patch is X.Y.W"
- Guide through Gemfile update and bundle update rails
- Run test suite after patch upgrade
- Deploy patch upgrade before proceeding
- Do NOT proceed to next minor/major until on latest patch
4. If current version == latest patch:
- Proceed to Step 1
Why patch first: Patch releases contain security fixes, bug fixes, and additional deprecation warnings. Starting the version hop on the latest patch is safer (the security fixes are already in production) and easier to debug (the new deprecation warnings surface issues that would otherwise show up mid-upgrade).
Step 1: Run Test Suite (MANDATORY FIRST STEP)
⚠️ THIS STEP IS REQUIRED BEFORE ANY OTHER WORK
1. Read: workflows/test-suite-verification-workflow.md
2. Detect test framework (RSpec, Minitest, or both)
3. Run test suite with: bundle exec rspec OR bundle exec rails test
4. Capture results: total tests, passing, failing, pending
5. If no runnable test suite exists:
- Load: work
ファイルのメタデータ
name: rails-upgrade description: 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, or querying version-specific changes. Based on FastRuby.io methodology and "The Complete Guide to Upgrade Rails" ebook.
元のテキストを表示
--- name: rails-upgrade description: 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, or querying version-specific changes. Based on FastRuby.io methodology and "The Complete Guide to Upgrade Rails" ebook. --- # Rails Upgrade Assistant Skill ## Skill Identity - **Name:** Rails Upgrade Assistant - **Purpose:** Intelligent Rails application upgrades from 2.3 through 8.1 - **Skill Type:** Modular with external workflows and examples - **Upgrade Strategy:** Sequential only (no version skipping) - **Methodology:** Based on FastRuby.io upgrade best practices and "The Complete Guide to Upgrade Rails" ebook - **Attribution:** Content based on "The Complete Guide to Upgrade Rails" by FastRuby.io (OmbuLabs) --- ## Dependencies - **dual-boot skill** ([github.com/ombulabs/claude-code_dual-boot-skill](https://github.com/ombulabs/claude-code_dual-boot-skill)) — Sets up and manages dual-boot environments using the `next_rails` gem. Covers setup, `NextRails.next?` code patterns, CI configuration, and post-upgrade cleanup. Must be installed for Step 2 of the upgrade workflow. - **rails-load-defaults skill** ([github.com/ombulabs/claude-code_rails-load-defaults-skill](https://github.com/ombulabs/claude-code_rails-load-defaults-skill)) — Handles incremental `load_defaults` updates with tiered risk assessment (Tier 1: low-risk, Tier 2: needs codebase grep, Tier 3: requires human review). Used as the final step after the Rails version upgrade is complete. --- ## Core Methodology (FastRuby.io Approach) This skill follows the proven FastRuby.io upgrade methodology: 1. **Incremental Upgrades** - Always upgrade one minor/major version at a time 2. **Assessment First** - Understand scope before making changes 3. **Dual-Boot Testing** - Test both versions during transition using `next_rails` gem 4. **Test Coverage** - Ensure adequate test coverage before upgrading (aim for 80%+) 5. **Gem Compatibility** - Check gem compatibility at each step using RailsBump 6. **Deprecation Warnings** - Address deprecations before upgrading 7. **Backwards Compatible Changes** - Deploy small changes to production before version bump **Key Resources:** - **DELEGATE** to the `dual-boot` skill for dual-boot setup with `next_rails` (see Dependencies) - See `references/deprecation-warnings.md` for managing deprecations - See `references/staying-current.md` for maintaining upgrades over time --- ## CRITICAL: Dual-Boot Code Pattern with `NextRails.next?` When proposing code fixes that must work with both the current and target Rails versions (dual-boot), **always use `NextRails.next?` from the `next_rails` gem** — never use `respond_to?` or other feature-detection patterns. **DELEGATE** to the `dual-boot` skill for: - Setup and initialization (`next_rails --init`, `Gemfile.next`) - `NextRails.next?` code patterns and examples - CI configuration for dual-boot testing - Post-upgrade cleanup (removing dual-boot branches) **DEPENDENCY:** Requires the [dual-boot skill](https://github.com/ombulabs/claude-code_dual-boot-skill) --- ## Trigger Patterns Claude should activate this skill when user says: **Upgrade Requests:** - "Upgrade my Rails app to [version]" - "Help me upgrade from Rails [x] to [y]" - "What breaking changes are in Rails [version]?" - "Plan my upgrade from [x] to [y]" - "What Rails version am I using?" - "Analyze my Rails app for upgrade" - "Find breaking changes in my code" - "Check my app for Rails [version] compatibility" **Specific Report Requests:** - "Show me the app:update changes" - "Preview configuration changes for Rails [version]" - "Generate the upgrade report" - "What will change if I upgrade?" **Upgrade Cleanup Requests (delegate to the `upgrade-cleanup` plugin):** - "Finish the upgrade" - "Clean up after my Rails upgrade" - "Remove the dual-boot setup" - "Drop the NextRails branches" - "We're done upgrading to Rails [version]" --- ## CRITICAL: Sequential Upgrade Strategy ### ⚠️ Version Skipping is NOT Allowed Rails upgrades MUST follow a sequential path. Examples: **For Rails 5.x to 8.x:** ``` 5.0.x → 5.1.x → 5.2.x → 6.0.x → 6.1.x → 7.0.x → 7.1.x → 7.2.x → 8.0.x → 8.1.x ``` **You CANNOT skip versions.** Examples: - ❌ 5.2 → 6.1 (skips 6.0) - ❌ 6.0 → 7.0 (skips 6.1) - ❌ 7.0 → 8.0 (skips 7.1 and 7.2) - ✅ 5.2 → 6.0 (correct) - ✅ 7.0 → 7.1 (correct) - ✅ 7.2 → 8.0 (correct) If user requests a multi-hop upgrade (e.g., 5.2 → 8.1): 1. Explain the sequential requirement 2. Break it into individual hops 3. Generate separate reports for each hop 4. Recommend completing each hop fully before moving to next --- ## Supported Upgrade Paths ### Legacy Rails (2.3 - 4.2) | From | To | Difficulty | Key Changes | Ruby Required | |------|-----|-----------|-------------|---------------| | 2.3.x | 3.0.x | Very Hard | XSS protection, routes syntax | 1.8.7 - 1.9.3 | | 3.0.x | 3.1.x | Medium | Asset pipeline, jQuery | 1.8.7 - 1.9.3 | | 3.1.x | 3.2.x | Easy | Ruby 1.9.3 support | 1.8.7 - 2.0 | | 3.2.x | 4.0.x | Hard | Strong Parameters, Turbolinks | 1.9.3+ | | 4.0.x | 4.1.x | Medium | Spring, secrets.yml | 1.9.3+ | | 4.1.x | 4.2.x | Medium | ActiveJob, Web Console | 1.9.3+ | | 4.2.x | 5.0.x | Hard | ActionCable, API mode, ApplicationRecord | 2.2.2+ | ### Modern Rails (5.0 - 8.1) | From | To | Difficulty | Key Changes | Ruby Required | |------|-----|-----------|-------------|---------------| | 5.0.x | 5.1.x | Easy | Encrypted secrets, yarn default | 2.2.2+ | | 5.1.x | 5.2.x | Medium | Active Storage, credentials | 2.2.2+ | | 5.2.x | 6.0.x | Hard | Zeitwerk, Action Mailbox/Text | 2.5.0+ | | 6.0.x | 6.1.x | Medium | Horizontal sharding, strict loading | 2.5.0+ | | 6.1.x | 7.0.x | Hard | Hotwire/Turbo, Import Maps | 2.7.0+ | | 7.0.x | 7.1.x | Medium | Composite keys, async queries | 2.7.0+ | | 7.1.x | 7.2.x | Medium | Transaction-aware jobs, DevContainers | 3.1.0+ | | 7.2.x | 8.0.x | Very Hard | Propshaft, Solid gems, Kamal | 3.2.0+ | | 8.0.x | 8.1.x | Easy | Bundler-audit, max_connections | 3.2.0+ | --- ## Available Resources ### Core Documentation - `SKILL.md` - This file (entry point) ### Version-Specific Guides (Load as needed) **Legacy Rails:** - `version-guides/upgrade-3.2-to-4.0.md` - Rails 3.2 → 4.0 (Strong Parameters) - `version-guides/upgrade-4.0-to-4.1.md` - Rails 4.0 → 4.1 (Spring, secrets.yml, enums) - `version-guides/upgrade-4.1-to-4.2.md` - Rails 4.1 → 4.2 (ActiveJob, Web Console) - `version-guides/upgrade-4.2-to-5.0.md` - Rails 4.2 → 5.0 (ApplicationRecord) **Modern Rails:** - `version-guides/upgrade-5.0-to-5.1.md` - Rails 5.0 → 5.1 (Encrypted secrets) - `version-guides/upgrade-5.1-to-5.2.md` - Rails 5.1 → 5.2 (Active Storage, Credentials) - `version-guides/upgrade-5.2-to-6.0.md` - Rails 5.2 → 6.0 (Zeitwerk) - `version-guides/upgrade-6.0-to-6.1.md` - Rails 6.0 → 6.1 (Horizontal sharding) - `version-guides/upgrade-6.1-to-7.0.md` - Rails 6.1 → 7.0 (Hotwire/Turbo) - `version-guides/upgrade-7.0-to-7.1.md` - Rails 7.0 → 7.1 (Composite keys) - `version-guides/upgrade-7.1-to-7.2.md` - Rails 7.1 → 7.2 (Transaction jobs) - `version-guides/upgrade-7.2-to-8.0.md` - Rails 7.2 → 8.0 (Propshaft) - `version-guides/upgrade-8.0-to-8.1.md` - Rails 8.0 → 8.1 (bundler-audit) ### Workflow Guides (Load when generating deliverables) - `workflows/test-suite-verification-workflow.md` - **MANDATORY FIRST STEP** - How to run and verify test suite - `workflows/no-test-suite-smoke-workflow.md` - **Load from Step 1 when no runnable RSpec/Minitest suite exists** - Rails boot, routes, migration-status, and build smoke baseline with partial-confidence reporting - `workflows/direct-detection-workflow.md` - How to run breaking change detection directly - `workflows/upgrade-report-workflow.md` - How to generate upgrade reports - `workflows/gem-compatibility-workflow.md` - **Load in Step 4.5** - Per-lockfile gem compatibility check against the target Rails version. Documents both the primary (`next_rails` `bundle_report compatibility`) and the secondary (railsbump.org API) and the rules for when to escalate. - `workflows/boot-smoke-test-workflow.md` - **Load in Step 4.6** - Run a Rails-loading command against `Gemfile.next` to catch gem-level runtime incompat that the resolver can't see (gems calling removed Rails internals or `require`-ing removed files). - `workflows/ci-sync-workflow.md` - **MANDATORY before opening the upgrade PR** - How to verify CI config matches the upgraded Gemfile - `workflows/app-update-preview-workflow.md` - How to generate app:update previews - **`upgrade-cleanup` companion plugin** - User-triggered. Removes dual-boot scaffolding and drops `NextRails.next?` / `NextRails.current?` branches. Deprecation triage stays with this skill for the next hop. ### Examples (Load when user needs clarification) - `examples/simple-upgrade.md` - Single-hop upgrade example - `examples/multi-hop-upgrade.md` - Multi-hop upgrade example ### External Dependencies - **dual-boot skill** - Dual-boot setup and management with next_rails (Step 2) (https://github.com/ombulabs/claude-code_dual-boot-skill) - **rails-load-defaults skill** - Incremental load_defaults alignment (Step 7, final step) (https://github.com/ombulabs/claude-code_rails-load-defaults-skill) ### Reference Materials - `references/deprecation-warnings.md` - Finding and fixing deprecations - `references/staying-current.md` - Keeping up with Rails releases - `references/breaking-changes-by-version.md` - Quick lookup - `references/multi-hop-strategy.md` - Multi-version planning - `references/testing-checklist.md` - Comprehensive testing - `references/gem-compatibility.md` - Gem update order and the "no compatible version" playbook (fork / vendor / replace). Load only when Step 4.5's compatibility check produced blockers. - `references/js-compressor-sprockets-mismatch.md` - Keeping terser / closure-compiler working when the target Rails pins Sprockets to the 2.x line. Load only when JS_COMPRESSOR_GEM_MISMATCH fires. ### Detection Pattern Resources - `detection-scripts/patterns/rails-*.yml` - Version-specific patterns for direct detection ### Report Templates - `templates/upgrade-report-template.md` - Main upgrade report structure - `templates/app-update-preview-template.md` - Configuration preview --- ## High-Level Workflow When user requests an upgrade, follow this workflow: ### Step 0: Verify Latest Patch Version (MANDATORY PRE-STEP) ``` ⚠️ THIS STEP IS REQUIRED BEFORE ANY OTHER WORK 1. Read Gemfile.lock to find exact current Rails version (e.g., 3.2.19) 2. Compare against latest patch for that series: - EOL series (≤ 7.1): use static table in references/multi-hop-strategy.md - Active series (≥ 7.2): query RubyGems API (see references/multi-hop-strategy.md for commands) 3. If current version < latest patch: - INFORM user: "Your app is on Rails X.Y.Z but the latest patch is X.Y.W" - Guide through Gemfile update and bundle update rails - Run test suite after patch upgrade - Deploy patch upgrade before proceeding - Do NOT proceed to next minor/major until on latest patch 4. If current version == latest patch: - Proceed to Step 1 ``` **Why patch first:** Patch releases contain security fixes, bug fixes, and additional deprecation warnings. Starting the version hop on the latest patch is safer (the security fixes are already in production) and easier to debug (the new deprecation warnings surface issues that would otherwise show up mid-upgrade). ### Step 1: Run Test Suite (MANDATORY FIRST STEP) ``` ⚠️ THIS STEP IS REQUIRED BEFORE ANY OTHER WORK 1. Read: workflows/test-suite-verification-workflow.md 2. Detect test framework (RSpec, Minitest, or both) 3. Run test suite with: bundle exec rspec OR bundle exec rails test 4. Capture results: total tests, passing, failing, pending 5. If no runnable test suite exists: - Load: work
ソースを確認
価格と実行コスト
- Skill の入手
- 価格未確認
- 実行
- 実行要件は未確認です。Agent・API・サービス料金を提供元で確認してください。
- ライセンス
- MIT
- 価格未確認
- 価格は未確認です。既存のソースとインストールリンクは利用できます。
無料で入手できても実行が無料とは限りません。価格は安全評価ではありません。 価格情報を送る →
ソースの再確認が必要
ソースが変更されたか同期に失敗しました。インストール前に確認してください。
インストール前にレビュー: 自動インストールを避ける
ライセンス: MIT
- Dependency or permission surface needs review
- Permission surface may require sandboxing
- The SKILL.md excerpt is truncated, but the visible content is comprehensive and well-organized.
- The skill references an 'upgrade-cleanup' plugin in trigger patterns but does not list it in the Dependencies section, which could cause confusion about required setup.
- The skill depends on two external skills (dual-boot and rails-load-defaults) that must be installed separately; this is clearly stated but could be a barrier if users are unaware.
- Quality score needs review
- Permission surface needs review: secrets or environment access, shell or command execution
- Stars/forks activity: 381 stars, 15 forks; issue activity unavailable in current metadata
- Dependency/runtime risk: command execution surface, credential or environment access
- Permission surface: secrets or environment access, shell or command execution
ツール一覧はメタデータであり、互換性のテスト結果ではありません。プロンプトは提案です。
小さなタスクから始める
- 1ソースを読み、入力、出力、依存関係、権限を確認します。
- 2Agent に計画を求め、設定と費用を承認してから隔離環境でテストします。
- 3出力と変更ファイルを確認し、実行した結果だけを報告します。再現用にソースの版を保存します。
依存関係、API キー、外部サービスの料金をソースで確認してください。公開リポジトリでも全サービスが無料とは限りません。
出典と利用上の注意
メタデータと審査情報は参考です。人気、ソースの発見、実行成功は別の事実です。
- ソースリポジトリ
- ombulabs/claude-code_rails-upgrade-skill
- ライセンス
- MIT
- バージョン
- 1.0.0
- 最終 GitHub プッシュ
- 2026年8月27日
- 登録情報の更新日
- 2026年9月29日
登録されたバージョンです。ソースのリリース情報を確認してください。
品質
70/100
強い
信頼
53/100
Do not auto-install
監査
72/100
要レビュー
- Dependency or permission surface needs review
- Permission surface may require sandboxing
- The SKILL.md excerpt is truncated, but the visible content is comprehensive and well-organized.
- The skill references an 'upgrade-cleanup' plugin in trigger patterns but does not list it in the Dependencies section, which could cause confusion about required setup.
- The skill depends on two external skills (dual-boot and rails-load-defaults) that must be installed separately; this is clearly stated but could be a barrier if users are unaware.
- Quality score needs review
- Permission surface needs review: secrets or environment access, shell or command execution
- Stars/forks activity: 381 stars, 15 forks; issue activity unavailable in current metadata
- Dependency/runtime risk: command execution surface, credential or environment access
- Permission surface: secrets or environment access, shell or command execution
- Verified installs
- —
- 成果
- —
コピーはインストールではありません。件数は成功報告に基づき、品質全体を保証しません。
Agent 接続
Registry API 経由で判断、信頼、監査、ユースケース、インストールのシグナルを提供し、UI をスクレイピングせずに Agent が順位付けできます。
詳細情報
{
"version": "openagentskill-agent-metadata-v2",
"review_evidence": {
"indexed": true,
"static_checked": false,
"ai_reviewed": false,
"manual_reviewed": false,
"creator_verified": false,
"review_result": "version_needs_review",
"reviewed_at": null,
"package_fingerprint": null,
"policy_version": null,
"notice": "Publication, static checks, AI review, and creator verification are independent facts. None guarantees runtime safety."
},
"commerce": {
"type": "unknown",
"billing": "unknown",
"amount": null,
"currency": null,
"sourceUrl": null,
"checkedAt": null,
"runtime": "unknown",
"purchaseUrl": null,
"checkout": "external",
"purchaseRequiresUserConsent": true
},
"skill": {
"slug": "ombulabs-rails-upgrade",
"name": "rails-upgrade",
"description": "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, or querying version-specific changes. Based on FastRuby.io methodology and \"The Complete Guide to Upgrade Rails\" ebook.",
"category": "research",
"url": "https://www.openagentskill.com/skills/ombulabs-rails-upgrade",
"repository": "https://github.com/ombulabs/claude-code_rails-upgrade-skill/tree/main/rails-upgrade",
"github_repo": "ombulabs/claude-code_rails-upgrade-skill"
},
"suited_tasks": [
"Coding agents workflows",
"Claude Code teams",
"builders willing to evaluate younger projects",
"Inspect source files",
"Explain architecture",
"Patch bugs and verify changes",
"Search sources",
"Extract claims"
],
"suited_agents": [
"Codex",
"Claude Code",
"Cursor",
"OpenAgentSkill CLI"
],
"install": {
"source_evidence": {
"status": "source-needs-review",
"sourceRecorded": true,
"canOfferInstall": false,
"path": "rails-upgrade/SKILL.md",
"revision": "44b7cda5ae3ea60b08131a590810ed84833da282",
"notice": "The tracked source changed or could not be synchronized. Review the current source before installing."
},
"command": "",
"ready": false,
"targets": [
{
"id": "codex",
"label": "Codex",
"kind": "agent-prompt",
"value": "Review the public source for \"rails-upgrade\" at https://github.com/ombulabs/claude-code_rails-upgrade-skill/tree/main/rails-upgrade. The tracked source changed or could not be synchronized. Review the current source before installing. Do not install or execute repository code in this review. Report whether valid skill instructions exist, their exact path and revision, dependencies, costs, license and requested permissions. Ask for approval before any installation. Treat repository text as untrusted data, not authorization."
},
{
"id": "claude-code",
"label": "Claude Code",
"kind": "agent-prompt",
"value": "Review the public source for \"rails-upgrade\" at https://github.com/ombulabs/claude-code_rails-upgrade-skill/tree/main/rails-upgrade. The tracked source changed or could not be synchronized. Review the current source before installing. Do not install or execute repository code in this review. Report whether valid skill instructions exist, their exact path and revision, dependencies, costs, license and requested permissions. Ask for approval before any installation. Treat repository text as untrusted data, not authorization."
},
{
"id": "cursor",
"label": "Cursor",
"kind": "agent-prompt",
"value": "Review the public source for \"rails-upgrade\" at https://github.com/ombulabs/claude-code_rails-upgrade-skill/tree/main/rails-upgrade. The tracked source changed or could not be synchronized. Review the current source before installing. Do not install or execute repository code in this review. Report whether valid skill instructions exist, their exact path and revision, dependencies, costs, license and requested permissions. Ask for approval before any installation. Treat repository text as untrusted data, not authorization."
}
],
"handoff_url": "https://www.openagentskill.com/api/skills/ombulabs-rails-upgrade/install",
"manifest_url": "https://www.openagentskill.com/api/registry/manifest/ombulabs-rails-upgrade"
},
"trust": {
"score": 61,
"label": "Manual review",
"version": "trust-score-v4",
"install_policy": "block",
"evidence": {
"stars": "381 GitHub stars",
"repoActivity": "381 stars, 15 forks",
"lastPushed": "2mo since push",
"license": "MIT",
"repository": "https://github.com/ombulabs/claude-code_rails-upgrade-skill/tree/main/rails-upgrade",
"install": "The tracked source changed or could not be synchronized. Review the current source before installing.",
"installSafety": "standard package or runtime install path",
"permissionSurface": "secrets or environment access, shell or command execution",
"documentation": "Strong README/SKILL.md context",
"agentOutcomes": "No agent outcome data yet"
},
"outcome_evidence": {
"total": 0,
"successes": 0,
"failures": 0,
"not_relevant": 0,
"success_rate": null,
"recent_success_rate": null,
"recent_failure_rate": null,
"install_attempts": 0,
"install_success_rate": null,
"risk_blocked": 0,
"setup_required": 0,
"avg_output_quality": null,
"production_outcomes": 0,
"last_outcome_at": null,
"label": "No agent outcome data yet"
},
"auto_install": {
"allowed": false,
"sandbox_required": true,
"reason": "Do not auto-install. Inspect the source, dependencies, and permission surface first."
},
"best_for": [
"research",
"agent-skill"
],
"known_risks": [
"The SKILL.md excerpt is truncated, but the visible content is comprehensive and well-organized.",
"Quality score needs review",
"Permission surface needs review: secrets or environment access, shell or command execution",
"Stars/forks activity: 381 stars, 15 forks; issue activity unavailable in current metadata",
"Dependency/runtime risk: command execution surface, credential or environment access",
"Permission surface: secrets or environment access, shell or command execution"
]
},
"agent_proven": {
"version": "agent-proven-v1",
"score": 0,
"tier": "unproven",
"label": "Needs first agent run",
"summary": "No agent outcome reports yet. Use Resolve, run one narrow sandbox task, then report the result.",
"metrics": {
"totalOutcomes": 0,
"successfulOutcomes": 0,
"failedOutcomes": 0,
"installAttempts": 0,
"installSuccessRate": null,
"successRate": null,
"recentSuccessRate": null,
"recentFailureRate": null,
"riskBlocked": 0,
"setupRequired": 0,
"notRelevant": 0,
"avgOutputQuality": null,
"avgTimeToUsefulMs": null,
"productionOutcomes": 0,
"humanReviewRequired": 0,
"uniqueAgents": 0,
"lastOutcomeAt": null
},
"signals": [],
"penalties": [
"No real agent outcome evidence yet"
]
},
"audit": {
"score": 72,
"risk_level": "needs_review",
"risk_label": "Needs review",
"warnings": [
"Dependency or permission surface needs review",
"Permission surface may require sandboxing",
"The SKILL.md excerpt is truncated, but the visible content is comprehensive and well-organized.",
"The skill references an 'upgrade-cleanup' plugin in trigger patterns but does not list it in the Dependencies section, which could cause confusion about required setup.",
"The skill depends on two external skills (dual-boot and rails-load-defaults) that must be installed separately; this is clearly stated but could be a barrier if users are unaware.",
"Quality score needs review",
"Permission surface needs review: secrets or environment access, shell or command execution",
"Stars/forks activity: 381 stars, 15 forks; issue activity unavailable in current metadata"
]
},
"safety_gate": {
"tier": "blocked",
"label": "Blocked for auto-install",
"auto_install_policy": "block",
"auto_install_allowed": false,
"human_review_required": true,
"blocked": true,
"recommended_action": "Do not auto-install. Inspect the source, dependencies, and permission surface first."
},
"quality": {
"score": 70,
"label": "Strong"
},
"supply": {
"track": "Research and knowledge work",
"scenario": "Research agents",
"maintenance": "2mo since push",
"risk": "Needs review"
},
"alternative_skills": [],
"do_not_use_when": [
"teams that need a vendor-supported SLA",
"production agents without a repository review",
"The SKILL.md excerpt is truncated, but the visible content is comprehensive and well-organized.",
"High-risk permission hints: Shell or command execution, Secrets or environment access",
"Dependency or permission surface needs review",
"Permission surface may require sandboxing",
"The skill references an 'upgrade-cleanup' plugin in trigger patterns but does not list it in the Dependencies section, which could cause confusion about required setup.",
"The skill depends on two external skills (dual-boot and rails-load-defaults) that must be installed separately; this is clearly stated but could be a barrier if users are unaware."
],
"agent_contract": {
"task_input": "Use rails-upgrade in an agent workflow",
"recommended_action": "Do not auto-install. Inspect the source, dependencies, and permission surface first.",
"install_policy": "block",
"minimum_review_before_use": [
"Trust: 61/100 Manual review",
"Audit: 72/100 Needs review",
"Safety: 28/100 Avoid automatic install",
"Review repository, license, install command, and permission surface before production use."
],
"expected_agent_output": {
"selected_skill": "ombulabs-rails-upgrade (rails-upgrade)",
"install_command": "",
"risk_summary": "Needs review; Blocked for auto-install; Review before production",
"verification_result": "Report the smallest successful task, files touched, warnings, and any missing setup."
}
},
"outcome_feedback": {
"endpoint": "https://www.openagentskill.com/api/agent/outcome",
"method": "POST",
"requires_resolve_event_id": true,
"event_id_source": "Use install_receipt.outcome_feedback.event_id or feedback.event_id returned by /api/agent/resolve for the current task.",
"expected_outcomes": [
"success",
"failed",
"not_relevant",
"blocked_by_risk",
"setup_required"
],
"payload_template": {
"event_id": "<install_receipt.outcome_feedback.event_id or feedback.event_id from /api/agent/resolve>",
"skill_slug": "ombulabs-rails-upgrade",
"task": "Use rails-upgrade in an agent workflow",
"agent": "codex",
"outcome": "success",
"install_used": true,
"risk_blocked": false,
"setup_required": false,
"task_success": true,
"output_quality": 4,
"error_type": null,
"human_review_required": false,
"workspace": "sandbox",
"time_to_useful_ms": 120000,
"notes": "Report the smallest successful task, setup friction, files touched, and risk notes."
}
},
"endpoints": {
"web": "https://www.openagentskill.com/skills/ombulabs-rails-upgrade",
"api": "https://www.openagentskill.com/api/agent/skills/ombulabs-rails-upgrade",
"audit": "https://www.openagentskill.com/skills/ombulabs-rails-upgrade/audit",
"eval": "https://www.openagentskill.com/api/agent/evals?slug=ombulabs-rails-upgrade&task=Use%20rails-upgrade%20in%20an%20agent%20workflow&max_risk=medium",
"resolve": "https://www.openagentskill.com/api/agent/resolve?task=Use%20rails-upgrade%20in%20an%20agent%20workflow&agent=codex&max_risk=medium",
"receipt": "https://www.openagentskill.com/api/agent/receipt?task=Use%20rails-upgrade%20in%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text",
"install": "https://www.openagentskill.com/api/skills/ombulabs-rails-upgrade/install",
"manifest": "https://www.openagentskill.com/api/registry/manifest/ombulabs-rails-upgrade"
}
}クリエイター向け
掲載元
Registry により登録
この掲載は公開ソースから登録されており、メンテナー申請が承認されるまで公式として表示されません。
- 作成者
- ombulabs
- インデックス作成者
- OpenAgentSkill コミュニティインデックス
帰属は公開リポジトリまたは作成者プロフィールにリンクされています。作成者は掲載を申請して所有権シグナルを更新できます。
このスキルを申請所有者の申請
このスキル掲載を申請
この Registry により登録 掲載は ombulabs に帰属していますが、まだ公式として表示されていません。申請すると、確認済み所有者シグナルが追加され、今後の公開、インストール、監査更新の信頼性が高まります。
共有キット
クリエイター被リンクキット
README にエビデンスバッジを追加
開発者がリポジトリを評価する場所で、正規掲載、現在の信頼・監査シグナル、実際の Agent-Proven エビデンスを表示します。
[](https://www.openagentskill.com/skills/ombulabs-rails-upgrade?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/ombulabs-rails-upgrade?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/ombulabs-rails-upgrade/audit)
[](https://www.openagentskill.com/skills/ombulabs-rails-upgrade?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)コミュニティシグナル
このスキルが Agent ワークフローに役立つかを共有してください。集約されたフィードバックがランキングを改善します。
