mise-tasks

name	mise-tasks
description	Add, modify, or invoke mise tasks (file tasks and TOML tasks); wire task help via usage directives; run tasks with mise run. Use when adding, modifying, running, or debugging tasks in a mise-managed project.

Mise Tasks

Use this skill when adding, modifying, or invoking mise tasks in any project that adopts mise as its task runner.

This skill complements the scripts skill (broader script authoring, testing, and integration workflow). When both apply, prefer the more specific rule here for task-runner specifics and defer to scripts for general script structure.

Discovery and Execution

• List tasks with mise tasks (alias mise tasks ls).
• Inspect a single task with mise tasks info <task>.
• Render task help with mise run <task> --help (or -h). See mise run and running tasks.

Authoring Conventions

Mise supports two task styles. Detect the style the project already uses and match it; do not introduce a second style without a clear reason.

File tasks

See file tasks.

• Place file tasks in the project's configured tasks directory; refer to the docs for the supported defaults and how task_config.includes overrides them.
• Make the file executable; mise auto-registers executable files in the tasks directory.
• Use a file extension that matches the task language/interpreter (for example .zsh, .sh, .js, .ts).
• Keep files named _default extensionless; mise default-task resolution breaks when _default has an extension.
• Before authoring a file task, assess whether any of its logic should be reusable across other tasks or scripts. When it should, extract the reusable code into a directory outside the mise-detected tasks directory and import it from the task file. Keep the task namespace populated only by tasks; let shared logic live alongside the project's other source code for clearer separation of concerns.

TOML tasks

See TOML tasks.

• Define TOML tasks as [tasks.<name>] tables (one table per task) in mise.toml or .mise.toml.
• Configure metadata (description, depends, env, sources, outputs, dir, usage, quiet, etc.) per task configuration.

Usage and Help

• Prefer mise's usage feature for argument parsing, option configuration, defaults, validation, and help on file tasks. Let usage own the task's interface; keep in-script code focused on the task's behavior rather than reimplementing argument parsing.
• Define the task interface with mise's usage directives appropriate to the task's language. Examples: #USAGE for shell file tasks, //USAGE for TypeScript file tasks, and the usage field on TOML tasks. See the Arguments section of the file-tasks docs.
• Rely on mise's native help rendering; do not implement custom help printing inside task scripts.
• Treat unknown or incomplete options as explicit errors.

Output

• Set tasks to quiet by default so mise does not prefix task output with [task-name]. Use quiet = true for TOML tasks and the equivalent #MISE quiet=true directive for file tasks (or whichever directive syntax the task's language uses, per task configuration).