mise-en-place

Appearance

mise generate task-stubs ​

Generate scripts that run mise tasks

Writes one executable stub per task into a directory, such as bin/test for the test task, that runs the task with mise. Pair them with mise generate install-script so contributors can run tasks without installing mise. When a task has subtasks, the parent's stub is written to <parent>/_default.

Hidden tasks and global tasks are skipped: the stubs are committed to the project, and global tasks come from each user's own config.

Flags ​

  • -d --dir <DIR> — Directory to create task stubs inside of

    Default: bin

  • -m --mise-bin <PATH> — mise executable the stubs run; defaults to mise from PATH

    Use --mise-bin ./bin/mise with a script from mise generate install-script. On Windows a path runs as written, so that script needs its .cmd launcher beside it; generate it with mise generate install-script --write ./bin/mise --windows. The default, mise, is a bare name that resolves from PATH and needs nothing extra.

    Default: mise

  • --windows-launcher <KIND> — What to write beside each stub for Windows to launch

    cmd writes <task>.cmd. cmd.exe re-parses the whole line before %* expands, so an argument containing & ^ | " %VAR% does not reach the task intact when the launcher is called from PowerShell.

    exe writes a native <task>.exe instead, which receives its arguments unchanged from every shell. It is a copy of the mise-shim.exe that ships with the Windows build, so it can only be generated on Windows, and it adds ~220KB per task to a directory that is normally committed.

    Choices: cmd, exe

    Default: cmd

  • -h --help — Print help

Examples ​

Write a stub for each task into ./bin

mise generate task-stubs

Make the stubs run the mise that mise generate install-script wrote

mise generate task-stubs --mise-bin ./bin/mise
MIT LicenseCopyright © 2026jdx.dev