skills.rest
ray-manaloto
ray-manalotoOFFICIAL
Explore all skills by this author →
GitHub

mise-migrate-from-asdf

Migrates .tool-versions projects from asdf to mise preserving pin and configs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrate a project from asdf to mise while preserving .tool-versions, respecting the global vs local configuration, and addressing common pitfalls in the migration process.

Core Features & Use Cases

  • Automates migration steps for projects using .tool-versions and asdf plugins, ensuring pins are preserved and misconfigurations are avoided.
  • Provides clear, step-by-step guidance for installation, activation, and global config migration.
  • Supports edge cases like asdf-go vs asdf-bash differences and deprecated plugin behavior.

Quick Start

Run mise migrate-from-asdf in your project directory to migrate from asdf to mise and preserve version pins.

Frequently Asked Questions about mise-migrate-from-asdf

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

FAQPage Schema
How do I migrate from asdf to mise without losing tool version pins?▼

Migrating from asdf to mise safely involves reading your existing .tool-versions file and asdf plugin configurations, preserving version pins while guiding installation and activation across shells.

Does mise support existing .tool-versions files from asdf?▼

Mise supports .tool-versions files natively. The migration process applies to projects with this file and asdf plugin configurations, automatically preserving your local and global tool version pins.

What is the best way to handle asdf global vs local config when switching to mise?▼

Handling asdf global vs local config when switching to mise requires a guided workflow that respects existing configuration boundaries, ensuring global and local tool pins migrate correctly without misconfiguration.

How do I recover from a partial asdf to mise migration?▼

Recovering from a partial asdf to mise migration relies on the workflow's validation steps and fallback recommendations, addressing edge cases like deprecated plugin behavior to safely restore or complete the process.

What are common gotchas when migrating dev tool configurations from asdf to mise?▼

Common gotchas when migrating dev tool configurations from asdf to mise include asdf-go vs asdf-bash differences, deprecated plugin behavior, and global vs local config misconfigurations, all addressed by the migration workflow.

Why should I migrate my devtool setup from asdf to mise?▼

Migrating your devtool setup from asdf to mise leverages a modern tool manager while ensuring existing version pins, plugin configurations, and global settings transition safely with clear validation steps.

Related Skills

Explore More Software Engineering Skills→
samhvw8samhvw8
14

mise-expert

Manage tool versions and environments with Mise configuration files.

Community
Advanced
ray-manalotoray-manaloto
1

mise-ide-activation

Guide IDE integration for mise using PATH shims, shell activation, native plugins, and asdf compatibility.

Official
Intermediate
ray-manalotoray-manaloto
1

mise-shell-activation

Generate shell activation snippets for Mise across bash, zsh, fish, nushell, elvish, xonsh, and PowerShell.

Official
Intermediate
MadBomberMadBomber
11

ruby-version-manager

Detect Ruby version managers and generate activation commands from project files.

Community
Intermediate