What is rigor-ruby-version-bump?

A workflow for updating the Ruby version used to develop Rigor while keeping the gem's supported Ruby range unchanged. Ruby is the programming language and runtime used by the project.

Use it when adopting a newer Ruby release, updating the project’s development-version files, and keeping the change together in one commit.

It prevents development-version markers from being confused with the versions the published gem supports. That avoids accidentally narrowing support or forcing contributors to use an unintended version.

How rigortype/rigor configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to rigortype/rigor. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/rigortype/rigor/master/.claude/skills/rigor-ruby-version-bump/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/rigortype/rigor

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/rigortype/rigor/rigor-ruby-version-bump/github.svg)](https://agentmods.dev/skills/rigortype/rigor/rigor-ruby-version-bump)

Your own site

<a href="https://agentmods.dev/skills/rigortype/rigor/rigor-ruby-version-bump"><img src="https://agentmods.dev/badge/skills/rigortype/rigor/rigor-ruby-version-bump/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/rigortype/rigor/rigor-ruby-version-bump"><img src="https://agentmods.dev/badge/skills/rigortype/rigor/rigor-ruby-version-bump.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,821 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00052	$0.02821
Opus 5.5	$0.00021	$0.01128
Sonnet 5.5	$0.00010	$0.00564
Haiku 4.5	$0.00005	$0.00282

Measured 11d ago against content hash ee5d4dfbc01a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

rigor-ruby-version-bump scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/rigor-ruby-version-bump/SKILL.md · 178 lines

How it starts

The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Bump the Ruby Version

Use this skill when the project's Ruby version needs to move (e.g. 4.0.4 → 4.0.5). The version is recorded in several independent places, and the first job is to understand that those places fall into two categories — conflating them is the mistake this skill exists to prevent.

Land the whole change as one commit so the markers never diverge in history.

Two kinds of marker — do not conflate them

Bumping every marker to the exact patch couples the development Ruby to the supported-range markers, which breaks CI and force-upgrades contributors. Keep the two groups separate.

Development Ruby — the exact patch the contributor shell runs. Flake-controlled; bump freely to any released patch.

flake.nix — the mkRuby version + re-derived hash.
.ruby-version — read by rbenv / chruby / asdf and by ruby/setup-ruby in CI.
.tool-versions — read by asdf / mise; a peer of .ruby-version.
AGENTS.md — the Flake Ruby version under "Development Environment".

Supported-range markers — express what Ruby the gem supports, not the dev patch. A patch bump MUST NOT touch these.

rigortype.gemspec — required_ruby_version ([">= 4.0.0", "< 4.1"]) — the binding contract for end users.
Gemfile — the ruby directive — a range mirroring the gemspec (ruby ">= 4.0.0", "< 4.1"), never an exact patch.
Gemfile.lock — the RUBY VERSION block — held at the supported floor (ruby 4.0.0), not the dev patch.
.github/workflows/ci.yml — the ruby: matrix — a minor series ("4.0"); ruby/setup-ruby resolves the patch.

Why the Gemfile directive must be a range, not an exact patch. Bundler treats ruby "x.y.z" as an exact match and aborts every bundle command when the running Ruby differs by even a patch. CI's setup-ruby installs whatever patch it currently ships (often a step behind the newest release), so an exact pin newer than that breaks CI; contributors not yet on the exact patch are likewise force-upgraded. A range — ruby ">= 4.0.0", "< 4.1" — accepts any 4.0.x and keeps the gemspec as the single source of truth for the supported range. Note that an exact ruby "4.0.0" is not a fix either: it would reject the Flake's own newer Ruby and break the dev shell.

Read the full file on GitHub · 178 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

11d ago First seen · 178 lines · 52 tokens per session scan A ee5d4dfbc01a

Subscribe to this mod's changes

rigor-ruby-version-bump is a skill published in the GitHub repository rigortype/rigor (107 stars, last pushed today), licensed MPL-2.0. It adds 52 tokens to every session and 2,821 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-26.

Languages Ruby

rigor-ruby-version-bump next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
rigor-ruby-version-bumprigortype/rigor	Skill	107	today	MPL-2.0	A	52	Claude Code
newclacky-ai/openclacky	Skill	1.2k	yesterday	MIT	A	10	Claude Code
rspec-conventionsrootstrap/rails_api_base	Skill	634	2d ago	MIT	A	82	Claude Code
dhh-rails-styledavekilleen/Dex	Skill	512	8d ago	MIT	A	115	Claude Code
ruby-patternssoftspark/ai-toolkit	Skill	179	10d ago	Apache-2.0	A	60	Claude Code
ruby-idiomsirahardianto/awesome-agv	Skill	158	23d ago	MIT	A	61	Claude Code, Codex
ruby-rulessoftspark/ai-toolkit	Skill	179	10d ago	Apache-2.0	A	48	Claude Code

rigor: Skill for Claude Code