mise — Dev Environment Manager

mise is a polyglot tool that replaces asdf/nvm/pyenv/direnv/make. It manages three things:

1. Tool versions — install and pin node, python, go, ruby, java, etc.
2. Environment variables — per-project env var management
3. Tasks — project task runner (like make/npm scripts)

How to use this skill

Identify which domain the user needs, then read only the relevant reference file:

If the request spans multiple domains, read the relevant reference files.

Key principles

1. Always clarify scope. When the user asks to install or use a tool, confirm whether they mean project-level (mise use <tool>) or global (mise use -g <tool>) before running commands. Project-level writes to ./mise.toml; global writes to ~/.config/mise/config.toml.

2. Prefer mise use over mise install. mise use both installs and pins the version in the config file. mise install only installs without pinning — it's mainly for pre-caching.

3. Use mise.toml format. This is mise's native config format and supports all features. .tool-versions is asdf-compatible but limited to tool versions only.

4. Check before acting. Run mise ls or mise config ls first to understand the current state before making changes.

5. Verify mise is available. Before running any mise command, run which mise to check availability. If not found, install it:

   curl https://mise.run | sh
   

   Then verify with mise --version before proceeding.

6. Follow the user's language. Respond in the same language the user is using. If they write in Chinese, reply in Chinese; if in English, reply in English.