rails-upgrade-assistant_skill

This skill analyzes Rails projects and generates stepwise upgrade reports for Rails 7.0 to 8.1, including deprecations and migration guidance.

Shell

31

GitHub Stars

3

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill steveclarke/dotfiles --skill rails-upgrade-assistant

.gitignore18 B
LICENSE.txt1.1 KB
SKILL.md5.0 KB

Overview

This skill analyzes Ruby on Rails applications and generates actionable, version-specific upgrade deliverables for Rails 7.0 through 8.1.1. It produces a detection script, parses real findings from your codebase, and emits a comprehensive upgrade report plus an app:update preview tailored to the actual files it scanned. The output focuses on breaking changes, deprecations, and step-by-step migration guidance.

How this skill works

I generate a version-aware bash detection script that scans your repository for known breaking changes and patterns, producing a findings file with file:line references. After you run that script and provide the findings, I parse the results and assemble an upgrade report and an app:update preview using the exact occurrences from your codebase. For multi-hop requests I enforce the required sequential upgrade path and produce separate reports for each hop.

When to use it

Preparing to upgrade a Rails app from any 7.0.x through 8.1.1 target
Planning a multi-hop upgrade (e.g., 7.0 → 8.1) and needing per-hop guidance
Verifying code for version-specific deprecations and breaking changes before CI runs
Generating an app:update preview showing real config diffs
Creating a prioritized list of code changes with file:line references for development sprints

Best practices

Always perform upgrades sequentially: 7.0 → 7.1 → 7.2 → 8.0 → 8.1; do not skip versions
Run the generated detection script on the actual codebase and supply the findings file before requesting final reports
Complete and test each hop fully before moving to the next hop in a multi-hop plan
Use the app:update preview to review config diffs in a branch and run your full test suite after applying changes
Flag and review custom or monkey-patched code manually — the tool flags but does not automatically fix bespoke logic

Example use cases

Single-hop upgrade: generate a detection script for 7.1 and get a focused report upgrading 7.0 → 7.1
Multi-hop plan: request reports for 7.0 → 7.1, 7.1 → 7.2, etc., produced one hop at a time
Detection-only: ask for the detection script and run it in CI to surface deprecations early
App:update preview only: provide findings and get a patch-like preview of config updates and recommended generator changes

FAQ

No. Rails upgrades must follow the sequence 7.0 → 7.1 → 7.2 → 8.0 → 8.1. The skill will break multi-hop requests into individual hops and produce separate reports.

What do I need to provide to get a full report?

Run the generated detection script in your repo and provide the resulting findings file (rails_{version}_upgrade_findings.txt). Reports are built from those real findings.

Will the tool edit my code automatically?

No. It generates precise change lists, migration steps, and an app:update preview. All edits should be reviewed and applied in your own branches.