Agent skill

Rails Upgrade

by recursecenter in recursecenter/community

Project conventions for Rails version upgrades in this app. An agent skill from recursecenter/community.

AGPL-3.0Auto-check passedBackend & APIs

Install Rails Upgrade

skills CLI
$ npx skills add recursecenter/community --skill rails-upgrade -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install recursecenter/community rails-upgrade --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/recursecenter/community.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/rails-upgrade .claude/skills/rails-upgrade && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
rails-upgrade
GitHub stars
117
Token cost
~719 tokens
SKILL.md length
305 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Project conventions for Rails version upgrades in this app. An agent skill from recursecenter/community.

  • Works in 2 steps: Do not use the dual-boot pattern → Carefully review every diff that rails…
  • Tasks that involve Backend development
  • SKILL.md covers 1. Do not use the dual-boot… and 2. Carefully review every diff…
  • Calls rails

What it does

Rails Upgrade is an agent skill from recursecenter/community. Project conventions for Rails version upgrades in this app. Follow these whenever planning or executing a Rails minor/major upgrade (e.g. 7.1 → 7.2, 7.2 → 8.0), in addition to any general rails-upgrade tooling.

Its SKILL.md is about 720 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering Backend development and Code migrations. The repository describes itself as: community.recurse.com. The licence is AGPL-3.0.

When your agent uses it

  • Tasks that involve Backend development
  • Tasks that involve Code migrations

Example prompts

  • “/rails-upgrade”

Workflow steps

2 steps, taken from the step headings in SKILL.md.

  1. Do not use the dual-boot pattern
  2. Carefully review every diff that rails app:update produces

What it can do on your machine

Read from SKILL.md and the folder at commit e6c2357. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • rails

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Rails Upgrade loads about 719 tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 305 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~56
When it runs · the whole SKILL.md, loaded when a task matches
~719

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from recursecenter/community at commit e6c2357, republished under its AGPL-3.0 licence (© recursecenter). 305 words, ~719 tokens.

Download SKILL.mdSave it as .claude/skills/rails-upgrade/SKILL.md (or your agent's skills folder).
name
rails-upgrade
description
Project conventions for Rails version upgrades in this app. Follow these whenever planning or executing a Rails minor/major upgrade (e.g. 7.1 → 7.2, 7.2 → 8.0), in addition to any general rails-upgrade tooling.

When upgrading Rails in this app, follow these two conventions. They override the defaults of any general-purpose Rails upgrade workflow.

1. Do not use the dual-boot pattern

Skip next_rails, Gemfile.next, NextRails.next? branches, and a dual-boot CI matrix. Deliver each Rails version upgrade as a single PR that bumps Rails and applies all required fixes together.

The team and app are small enough that the overhead of maintaining a dual-boot environment (extra lockfile, conditional Gemfile, doubled CI runtime, code branches that have to be cleaned up later) is not worth the safety it adds. A single-PR upgrade is simpler to review, deploy, and revert.

For breaking-change fixes that would normally need a NextRails.next? branch in a dual-boot world, apply the new-version-only API directly in the same PR as the Rails bump — both changes ship together.

2. Carefully review every diff that rails app:update produces

rails app:update is interactive; for each conflicting file it offers Y/n/d/h. Use d to view the diff and then decide per file. Three categories:

  • Take stock changes when they are real improvements with no app-specific cost (e.g. modern Puma threading defaults, adding :email to filter_parameter_logging, new useful defaults that don't conflict with custom config).
  • Keep our version when stock generator output would erase app-specific configuration (custom log_tags, hosts allowlist, asset paths, CORS policy, frame_ancestors, queue_adapter, exceptions_app, custom URL options, environment-specific deploy concerns, etc.).
  • Cherry-pick lines worth taking and leave everything else untouched.

Do not just n-decline every conflict. That shortcut quietly accumulates config drift — your config files keep aging away from current Rails defaults, and you lose legitimate improvements baked into the updated generator templates.

A reliable workflow when working through app:update non-interactively (e.g. via Claude Code):

bash
# 1. Back up the conflict files
mkdir -p /tmp/<app>-pre-update
cp <each conflict file> /tmp/<app>-pre-update/<same path>

# 2. Force-write stock templates
bin/rails app:update --force

# 3. Per-file: diff stock vs backup
diff -u /tmp/<app>-pre-update/<file> <file>

# 4. Decide per file: keep stock, restore backup, or merge selectively
cp /tmp/<app>-pre-update/<file> <file>   # restore mine
# (or leave stock in place, or edit by hand to merge)

This produces one reviewable diff per file instead of the interactive prompt and makes the per-file decisions easy to discuss and document in the PR.

© recursecenter, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/rails-upgrade of recursecenter/community.

Open the folder on GitHubat commit e6c2357

Compare with similar skills

Rails Upgrade next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Rails Upgrade compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Rails Upgrade this skillrecursecenter/community117—~719Automated safety check: PassAGPL-3.0
Framework Migration AssistantArabelaTso/Skills-4-SE253—~1.9kAutomated safety check: PassApache-2.0
Groovy 5 Developer Guideapache/grails-core2.9k—~3kAutomated safety check: PassApache-2.0
Neo4j Spring Data Skillneo4j-contrib/neo4j-skills114—~3.7kAutomated safety check: NotesMIT
Deprecated API UpdaterArabelaTso/Skills-4-SE253—~2.8kAutomated safety check: PassApache-2.0
Infer Conventionsanonaddy/anonaddy4.9k5 repos~3.1kAutomated safety check: PassMIT

Similar skills

  • Framework Migration Assistant

    ArabelaTso/Skills-4-SE

    Automatically migrate Python web applications between frameworks (Flask → FastAPI, Django → FastAPI).

    253 GitHub stars~1.9k tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed
  • Groovy 5 Developer Guide

    apache/grails-core

    Guidance for Groovy 5 work in Grails projects: syntax, closures, traits, DSLs, metaprogramming, Spock tests, static compilation and Java 21 integration.

    2.9k GitHub stars~3k tokensUpdated today
    DevelopmentAuto-check passed
  • Neo4j Spring Data Skill

    neo4j-contrib/neo4j-skills

    A skill your agent uses when building Spring Boot applications with Neo4j using Spring Data Neo4j (SDN 7.x/8.x) — @Node entity mapping, @Relationship, @RelationshipProperties, Neo4jRepository…

    114 GitHub stars~3.7k tokensUpdated yesterday
    Backend & APIsAuto-check: notes
  • Deprecated API Updater

    ArabelaTso/Skills-4-SE

    Identify and replace deprecated API usage in source code with modern alternatives.

    253 GitHub stars~2.8k tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed
  • Infer Conventions

    anonaddy/anonaddy

    A skill your agent uses to analyze how a Laravel application is actually written and record its conventions as shared rules.

    4.9k GitHub starsUsed in 5 repos~3.1k tokens
    Backend & APIsAuto-check passed
  • Contributor guide for step three of adding a syncable entity to the Twenty server: write the validator, the migration action builder and the orchestrator wiring.

    58k GitHub stars~3.3k tokensUpdated today
    Backend & APIsAuto-check passed

Questions about Rails Upgrade

What does Rails Upgrade do?

Project conventions for Rails version upgrades in this app. An agent skill from recursecenter/community. Rails Upgrade is an agent skill from recursecenter/community. Project conventions for Rails version upgrades in this app.

When should I use Rails Upgrade?

Rails Upgrade fits situations like: tasks that involve Backend development; tasks that involve Code migrations.

How do I install Rails Upgrade in Claude Code?

Run `npx skills add recursecenter/community --skill rails-upgrade -a claude-code`. Or copy the skill folder (.claude/skills/rails-upgrade in recursecenter/community) into .claude/skills/rails-upgrade in your project. Claude Code loads it when a task matches its description.

How do I install Rails Upgrade in Codex?

Run `npx skills add recursecenter/community --skill rails-upgrade -a codex`. Or copy the skill folder (.claude/skills/rails-upgrade in recursecenter/community) into .agents/skills/rails-upgrade in your project. Codex loads it when a task matches its description.

Can I use Rails Upgrade in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add recursecenter/community --skill rails-upgrade -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rails-upgrade, .gemini/skills/rails-upgrade, .github/skills/rails-upgrade and .opencode/skills/rails-upgrade in your project.

What does Rails Upgrade need to run?

Going by SKILL.md and its folder, Rails Upgrade needs the command-line tools its instructions call (rails).

Does Rails Upgrade access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Rails Upgrade safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Rails Upgrade use?

Rails Upgrade is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Rails Upgrade use?

About 719 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Rails Upgrade?

Skills that share tags, products or a category with Rails Upgrade: Framework Migration Assistant (ArabelaTso/Skills-4-SE, 253 stars), Groovy 5 Developer Guide (apache/grails-core, 2.9k stars), Neo4j Spring Data Skill (neo4j-contrib/neo4j-skills, 114 stars) and Deprecated API Updater (ArabelaTso/Skills-4-SE, 253 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Rails Upgrade?

recursecenter (a GitHub organization) maintains it in recursecenter/community, which has 117 GitHub stars. The repository was last updated on September 29, 2026.

Source: recursecenter/community on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.