mise

Manages project tools, tasks, and environment variables via mise.toml.

2|Updated Jun 7, 2022
One-click install
npx skills add https://github.com/SebasAren/dotfiles --skill mise-sebasaren
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mise
Source: https://github.com/SebasAren/dotfiles/tree/main/pi/.pi/agent/skills/mise
Command: npx skills add https://github.com/SebasAren/dotfiles --skill mise-sebasaren

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes and simplifies project environment setup by managing runtime installations, per-project environment variables, and repeatable project tasks from a single mise.toml file so developers avoid juggling multiple version managers and ad-hoc scripts.

Core Features & Use Cases

  • Tool Version Management: Install, list, switch, and upgrade language runtimes and CLIs (node, python, go, etc.) with registry and backend support.
  • Task Runner & CI Patterns: Define reproducible tasks, dependencies, file sources/outputs, and watch or run tasks across development and CI workflows.
  • Per-project Environment Configuration: Manage env vars, local overrides, and environment-specific configs with trust and doctor checks.
  • Use Case: Initialize a repository with mise init, declare node and python versions and build/test tasks in mise.toml, run mise install to provision tools, and use mise run test in CI.

Quick Start

Initialize the current project with mise init to create mise.toml, then run mise install to provision declared tools and mise run to execute tasks.

Frequently Asked Questions about mise

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

FAQPage Schema
How do I manage multiple runtime versions for a development project?

Manage multiple runtime versions by declaring language tools like node or python in a mise.toml file. The manager installs and switches runtimes per project, eliminating the need to juggle multiple version managers.

What's the best way to define and run reproducible project tasks in CI?

Define reproducible project tasks by specifying dependencies and file sources in a mise.toml configuration. You can then execute these defined tasks across development and CI workflows using the run command.

Can I set per-project environment variables without ad-hoc shell scripts?

Set per-project environment variables directly within your mise.toml configuration. The manager applies these environment variables upon shell activation, allowing local overrides through a separate mise.local.toml file.

How does tool versioning work with backends like registry, cargo, and npm?

Tool versioning supports multiple backends including registry, aqua, cargo, npm, and pipx. You declare the desired tool versions in your configuration file, and the manager provisions them automatically during installation.

Do I need shell activation to load environment variables from mise.toml?

Shell activation is required to load environment variables defined in your mise.toml configuration. Once the shell is activated, the manager automatically applies the project-level environment setup and local overrides.

How do I initialize a repository to use a unified tool and environment manager?

Initialize a repository by running the init command to create a mise.toml file. After declaring your tools and tasks, run the install command to provision the declared runtimes and execute tasks.