Generate mise.toml configs for dev environments

Mise Configurator creates or updates mise.toml configurations for local development and CI/CD environments. It helps standardize runtime versions, simplify project onboarding, and bring multiple language toolchains into one configuration. It also supports migration from existing version managers and version files rather than ignoring the project's established choices.

The workflow first inspects repository context. Relevant files include package.json, pnpm-lock.yaml, pyproject.toml, requirements.txt, go.mod, Cargo.toml, .tool-versions, Dockerfile, and CI definitions. These supply evidence about languages, package managers, and pinned versions. The resulting configuration should contain the tools the project actually needs and remain minimal and readable.

Existing version pins take priority. If the repository does not declare a version, the skill asks for an explicit target before pinning it. Shared production configurations use concrete versions rather than floating latest or lts aliases unless those aliases are expressly requested. Stable releases and production requirements inform the choice, but illustrative versions are not a reason to overwrite a repository's current pins.

Use it when creating or maintaining mise.toml, setting up CI runtimes, standardizing tool versions across a team or monorepo, or migrating from asdf, nvm, pyenv, or .tool-versions. It covers mixed-language projects as well as individual runtime setups.

The configuration still requires validation in the actual operating system, shell, and CI platform. Runtime availability can vary, and niche tools or plugins may need manual adjustment. The skill requires clarification when inputs, permissions, or safety boundaries are missing. Generated shell commands should be reviewed before execution, and pipeline changes require confirmation of CI/CD permissions in an authorized repository.

Inputs include repository manifests, lockfiles, existing version declarations, requested target versions, and any CI integration requirements. The main output is a valid, copyable mise.toml configuration with a small set of appropriate tool entries. Bootstrap instructions explain how to trust and install the declared tools:

mise trust
mise install

When requested, the skill also produces pipeline examples with runtime installation and caching. Configuration patterns include a Node.js and pnpm toolchain, plus Python and Poetry used in GitHub Actions. Their role is to illustrate configuration structure and workflow integration.

Troubleshooting starts with checking lockfiles and pinned versions when the wrong runtime is selected. Slow CI installations call for cache layers and reuse of mise cache directories. A missing registry tool requires checking plugin support or arranging a manual installation instead of adding an unusable entry.

The named runtimes and tools include Node.js, Python, Go, Rust, Java, Bun, Terraform, pnpm, and Poetry. GitHub Actions examples use jdx/mise-action alongside checkout, dependency installation, and the project's verification command. Existing Docker and CI files can also inform environment detection.

Related references cover Docker development environments, advanced GitHub Actions templates, and monorepo architecture. These complement toolchain configuration when the surrounding environment needs more extensive work.

It is suited to developers and teams seeking consistent runtime versions for local work and CI. It also supports multi-package repositories where a shared configuration can reduce version drift while respecting the versions already declared by the project.