mise

Mise is a next-gen, cross-format dev tool for the...

11|5|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/rbergman/dark-matter-marketplace --skill mise
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mise
Source: https://github.com/rbergman/dark-matter-marketplace/tree/main/plugins/workflow/skills/mise
Command: npx skills add https://github.com/rbergman/dark-matter-marketplace --skill mise

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mise provides a unified, declarative approach to managing multiple tool versions per project, replacing ad-hoc installs with predictable, repository-scoped configurations.

Core Features & Use Cases

  • Per-project pinning: Pin tool versions in a .mise.toml for consistent environments across teammates.
  • Direnv integration: Work per-directory with environment variables isolated from tooling, reducing conflicts.
  • Workspace and global scope: Manage project, workspace, and global tool configurations to fit your workflow.
  • CI/CD and onboarding: Reproduce local dev environments in CI with the same toolchain.

Quick Start

Install Mise with the recommended installer: curl https://mise.run | sh Configure your shell to load mise and direnv, then add the recommended hooks:

~/.zshrc - recommended order

eval "$(mise activate zsh)" eval "$(direnv hook zsh)"

fish: ~/.config/fish/config.fish

mise activate fish | source direnv hook fish | source See the repository for full setup options.

Frequently Asked Questions about mise

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

FAQPage Schema
How do I manage per-project tool versions for consistent local development?

You can manage per-project tool versions by pinning them in a .mise.toml file, ensuring consistent environments across teammates. This declarative approach replaces ad-hoc installs with predictable, repository-scoped configurations.

Does mise integrate with direnv to separate environment variables from tooling?

Yes, mise integrates with direnv to isolate environment variables from tooling per directory. You configure your shell to load both tools, using mise for version management and direnv for environment variable management.

How do I reproduce my local dev environment in CI pipelines?

To reproduce local dev environments in CI, use mise to apply the same toolchain specified in your .mise.toml. This ensures CI pipelines use the exact per-directory tool pinning configured for local development.

Can I configure tool version management across workspace, project, and global scopes?

Yes, you can manage tool configurations across global, workspace, and project levels. This hierarchical scoping allows you to set base versions globally while overriding them with specific versions in workspace or project .mise.toml files.

What is the best way to set up shell hooks for tool version management?

The best way to set up shell hooks is adding eval "$(mise activate zsh)" and eval "$(direnv hook zsh)" to your ~/.zshrc. For fish, use mise activate fish | source and direnv hook fish | source in config.fish.