mise-migrate-from-rbenv

Migrate Ruby version management from rbenv to mise using project pins.

1|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ray-manaloto/claude-code-marketplace --skill mise-migrate-from-rbenv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mise-migrate-from-rbenv
Source: https://github.com/ray-manaloto/claude-code-marketplace/tree/main/mise-toolkit/skills/mise-migrate-from-rbenv
Command: npx skills add https://github.com/ray-manaloto/claude-code-marketplace --skill mise-migrate-from-rbenv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrating from rbenv to mise by reading existing .ruby-version files, handling rbenv-gemset, and cleanly tearing down ~/.rbenv so you can adopt mise for Ruby version management.

Core Features & Use Cases

  • Inventory and assess rbenv state across projects (installed rubies, current version, global pin).
  • Generate per-project mise.toml mappings and enable idiomatic readers for .ruby-version and Gemfile pins.
  • Swap shell RC configurations and verify rubies map to project pins; uninstall rbenv safely.

Quick Start

Follow the migration plan to switch from rbenv to mise in your shell and project configurations.

Frequently Asked Questions about mise-migrate-from-rbenv

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate from rbenv to mise while keeping my Ruby version pins?

To migrate from rbenv to mise, the process reads existing .ruby-version files and reconfigures tooling to generate a per-project mise.toml, ensuring your Ruby version pins remain intact across local development and CI.

What is the best way to handle rbenv-gemset when switching to mise?

When switching to mise, existing rbenv-gemset configurations are inventoried and mapped into per-project mise.toml files, allowing idiomatic readers to manage Gemfile pins and replace gemset dependencies.

How do I safely uninstall rbenv after switching to mise?

Safely uninstalling rbenv involves generating per-project mise.toml mappings, swapping shell RC configurations, verifying rubies map to project pins, and cleanly tearing down ~/.rbenv only after validation.

Does migrating to mise require updating my shell rc and bundler config?

Yes, migrating to mise requires swapping shell RC configurations to point to mise, alongside adjusting bundler and project config settings to enable idiomatic readers for .ruby-version and Gemfile pins.

Can I use mise for Ruby version management in CI environments previously using rbenv?

Yes, mise applies Ruby version management to CI environments by reading existing project pins and reconfiguring tooling, replacing rbenv-gemset dependencies with a unified mise.toml configuration.