skill-rails-upgrade
Analyze Rails apps and provide upgrade assessments
npx skills add sickn33/agentic-awesome-skills --skill skill-rails-upgrade --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
## When to Use This Skill Analyze Rails apps and provide upgrade assessments Use this skill when working with analyze rails apps and provide upgrade assessments. # Rails Upgrade Analyzer Analyze the current Rails application and provide a comprehensive upgrade assessment with selective file merging. ## Step 1: Verify Rails Application Check that we're in a Rails application by looking for these files: - `Gemfile` (must exist and contain 'rails') - `config/application.rb` (Rails application config) - `config/environment.rb` (Rails environment) If any of these are missing or don't indicate a Rails app, stop and inform the user this doesn't appear to be a Rails application. ## Step 2: Get Current Rails Version Extract the current Rails version from: 1. First, check `Gemfile.lock` for the exact installed version (look for `rails (x.y.z)`) 2. If not found, check `Gemfile` for the version constraint Report the exact current version (e.g., `7.1.3`). ## Step 3: Find Latest Rails Version Use the GitHub CLI to fetch the latest Rails release: ```bash gh api repos/rails/rails/releases/latest --jq '.tag_name' ``` This returns the latest stable version tag (e.g., `v8.0.1`). Strip the 'v' prefix
- When to Use This Skill
- Step 1: Verify Rails Application
- Step 2: Get Current Rails Version
- Step 3: Find Latest Rails Version
- Step 4: Determine Upgrade Type
- Step 5: Fetch Upgrade Guide
- Step 6: Fetch Rails Diff
- Step 7: Check JavaScript Dependencies
- 7.1: Identify JS Package Manager
- 7.2: Check Rails-Related JS Packages
- 7.3: Check for Updates
- 7.4: Check Importmap Pins (if applicable)
- 7.5: JS Dependency Summary
- Step 8: Generate Upgrade Summary
gh api repos/rails/rails/releases/latest --jq '.tag_name' gh api repos/rails/rails/tags --jq '.[0:10] | .[].name' Check for package.json (npm/yarn) ls package.json 2>/dev/null Check for importmap (Rails 7+) ls config/importmap.rb 2>/dev/null Extract current versions of Rails-related packages cat package.json | grep -E '"@hotwired/|"@rails/|"stimulus"|"turbo-rails"' || echo "No Rails JS packages found" Using npm npm outdated @hotwired/turbo-rails @hotwired/stimulus @rails/actioncable @rails/activestorage 2>/dev/null
What does the skill-rails-upgrade skill do?
Analyze Rails apps and provide upgrade assessments
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill skill-rails-upgrade --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.