mise-lang-ruby-gems

Manage per-project Ruby gems with Bundler and mise.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ruby gem management is often global and brittle, leading to version drift and conflicts across development, CI, and multiple Ruby versions. This Skill teaches how to use Bundler together with mise to pin gems per project and store dependencies in a vendor/bundle layout for reproducible installs.

Core Features & Use Cases

  • Project-scoped gem installation via Bundler and vendor/bundle to avoid cross-project conflicts.
  • Integration with mise.toml to manage tooling (rubocop, solargraph, etc.) and to support gem: backends when appropriate.
  • Guidance on upgrading/downgrading gems, configuring path settings, and emitting consistent binstubs for contributors.

Quick Start

Create a Gemfile for your project and run mise install to bootstrap a per-project bundle in vendor/bundle.

Frequently Asked Questions about mise-lang-ruby-gems

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

FAQPage Schema
How do I isolate Ruby gems per project to prevent version conflicts?

You isolate Ruby gems per project by configuring Bundler to install dependencies into a local vendor/bundle path and using mise to scope Ruby versions and tools. This ensures deterministic gem versions across developers and CI environments.

Why does my Ruby gem version drift between development and CI environments?

Gem version drift occurs when dependencies are installed globally without project isolation. Using Bundler with a vendor/bundle path and mise.toml pins gem versions per project, ensuring consistent installs across multiple Ruby versions and environments.

How do I configure Bundler to use a vendor/bundle path with mise?

You configure Bundler to use a vendor/bundle path by setting the bundle path in your project and managing tool versions through mise.toml. This combination scopes gems and binstubs locally for reproducible dependency management.

Can I manage multiple Ruby versions and their gems in the same project?

Yes, you can manage multiple Ruby versions and their gems by using mise to define Ruby versions in mise.toml and Bundler to install gems into a per-project vendor/bundle. This provides isolated dependency sets for each environment.

Does mise work with Bundler for Ruby dependency management?

Yes, mise works with Bundler by using mise.toml to scope tooling and Ruby versions while Bundler handles Gemfile-based gem installation into vendor/bundle. This integration supports gem backends and emits consistent binstubs for contributors.

What is the best way to avoid cross-project gem conflicts in Ruby?

The best way to avoid cross-project gem conflicts is project-scoped gem installation via Bundler into vendor/bundle, combined with mise for tool version management. This prevents global dependency pollution and ensures deterministic installs.