mise-toolkit

Detect the user's shell and add `mise activate` to their shell rc file

Install AI CLIs (claude, codex, aichat, gemini) via mise with redacted API key env vars

Walk the user through getting and setting API keys for claude, codex, and gemini — securely, never writing plaintext

Build the jdx/mise Rust binary via the mise task

Generate devcontainer.json + Codespaces prebuild config for zero-cold-start onboarding

Use when setting up AI CLIs (Claude, Codex, Gemini, aichat) via mise — "install claude code via mise", "set up AI CLIs for this project", "add an ai-status task", "configure OpenAI and Anthropic keys", or "/mise-ai-init". Picks which CLIs to install, writes the [env] + [redactions] blocks with correct redaction, sets up the ai-status task, and hands off to /mise-ai-keys for the actual key-setting step. Never writes plaintext secrets to any file.

Use when implementing, modifying, or reviewing tool backends in the jdx/mise Rust codebase under src/backend/** or core plugins in src/plugins/core/**. Triggers on "add a backend to mise", "fix the cargo backend", "implement install_version_impl", "review my backend PR", or any work touching the Backend trait. Knows the trait contract, the cross-backend conventions, and the registry mapping rules.

Use when a mise.toml is broken or behaving unexpectedly. Triggers on "mise isn't working", "mise doctor shows errors", "why is my tool version wrong", "mise trust issues", "config not loading", "mise.toml not detected", or after the user runs mise dr and gets warnings. Diagnoses configuration, hierarchy, trust, and activation problems.

Use when setting up C++ tooling for a project via mise — "set up cmake", "add ninja and ccache", "I need a fast linker", "wire up clang-format and clang-tidy", "what should my C++ mise.toml look like", or "/mise-cpp-init". Surveys the project for C++ artifacts, picks cmake / ninja / ccache / linker / package manager / clang-tools versions, and proposes a complete mise.toml with env var wiring for the golden trio.

Use when deciding how to deploy mise — "should I use Docker", "set this up in a container", "devcontainer for this project", "deploy mise to production", "mise in CI", or "what's the best way to run mise here". Picks the right model (host / Docker / devcontainer / Codespaces / CI runner / dotfiles) based on project shape, team constraints, and IDE requirements, then coordinates with mise-integration-architect for the mise.toml side and points at the right commands for the container/IDE side.

A 60-second pitch for mise aimed at zero-knowledge users — what it is, what it replaces, why it's better, what it isn't, and the smallest possible mise.toml. Use whenever the user asks "what is mise", "is mise worth it", "should I try mise", or seems unsure whether to adopt it.

The full mise [env] system — _.file (dotenv/json/yaml), _.path, _.source, _.<plugin>, tools=true lazy eval, required vars with help text, redactions, config_root resolution, and array-of-tables for multiple directives. Use whenever the user works on env vars in mise.toml, hits a "var not loaded" issue, or needs secrets/dynamic env handling.

The CRITICAL distinction between system packages (apt/brew/dnf — libssl, libpq, build-essential) and dev tools (mise — node, python, cmake, ripgrep). The

Cross-cutting overview of how to wire mise into every major IDE — VSCode, JetBrains, Neovim, Xcode, Zed, Sublime Text. The "if you're not sure where to start" entry point that points to per-IDE skills for depth. Use when a user says "how do I make my IDE see mise".

Every way to install mise itself — curl/sh, brew, apt, dnf, pacman, snap, nix, winget, scoop, choco, MacPorts, source, Docker. Plus uninstall, upgrade, and the install paths each method uses. Use when installing mise on a new machine, recommending an install method, or troubleshooting "command not found" after install.

6 hooks across 3 events