with one click
mise-tasks
Create and manage mise file tasks in the scripts/ directory
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Create and manage mise file tasks in the scripts/ directory
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | mise-tasks |
| description | Create and manage mise file tasks in the scripts/ directory |
This project uses mise for task running. Tasks are defined as
executable scripts in the scripts/ directory (configured via [task_config] in mise.toml).
scripts/ as executable bash scripts (no file extension)scripts/build/vscode becomes mise run build:vscode#MISE metadata comments#!/usr/bin/env bash
#MISE description="Short description of what this task does"
#MISE sources=["optional/glob/**/*.ext"]
#MISE outputs=["optional/output/path"]
#MISE depends=["optional:dependency"]
set -euo pipefail
# task implementation here
All #MISE directives go at the top of the file, after the shebang:
description (required) - shown in mise tasks outputsources - file globs; if set with outputs, mise skips re-runs when sources haven't changedoutputs - output files for staleness checkingdepends - tasks that must complete firstalias - short name for mise run <alias>dir - override working directory (default: project root)Subdirectories under scripts/ create colon-separated task names automatically.
Use this to organise related tasks by domain or action:
scripts/
├── build/
│ ├── vscode # mise run build:vscode
│ └── cli # mise run build:cli
├── link/
│ └── vscode # mise run link:vscode
└── test/
├── unit # mise run test:unit
└── integration # mise run test:integration
Group by what the task does (build, test, link, deploy) rather than what it
targets. This keeps the task list scannable in mise tasks output since tasks
are sorted alphabetically by name.
A file named _default inside a group directory becomes the bare group command.
This is useful when a group has an obvious "main" action:
scripts/
└── test/
├── _default # mise run test (runs this)
├── unit # mise run test:unit
└── integration # mise run test:integration
The _default task typically either runs all sub-tasks via depends, or
implements the most common case directly:
#!/usr/bin/env bash
#MISE description="Run all tests"
#MISE depends=["test:unit", "test:integration"]
set -euo pipefail
scripts/build/, scripts/link/)_default for the group's primary/aggregate actionchmod +x)#!/usr/bin/env bashset -euo pipefail#MISE description="..."mise tasks that the task appearsmise run unless it supports a --dry-run flag