mise-tasks_skill

Overview

This skill orchestrates multi-step project workflows using mise [tasks] with dependency management, argument handling, file tracking, and execution controls. It helps define, run, and cache tasks inside .mise.toml to automate builds, tests, releases, and deployment pipelines. The skill focuses on producing discoverable task descriptions so AI agents and CI tooling choose the right tasks reliably.

How this skill works

The skill generates and inspects mise task definitions: task metadata (description, alias, dir, env), dependency graphs (depends, depends_post, wait_for), and advanced fields (usage args, sources/outputs, confirm/raw/quiet). It evaluates when tasks should run via file-based sources/outputs caching and orchestrates parallel, sequential, or conditional execution. It also prepares hidden helper tasks, watch configurations, and monorepo path-scoped tasks.

When to use it

• You need to author or update .mise.toml tasks for CI, release, or local workflows
• You must express pre/post dependencies or parallel validation steps
• You want argument parsing and usage-driven task scripts
• You need file-tracking to skip unchanged work or force runs
• You want to add hidden verification tasks or environment-scoped tool versions
• You are designing monorepo or workspace-scoped task discovery and orchestration

Best practices

• Write rich task descriptions that state action, prerequisites, side effects, and recommended phase
• Prefer usage spec for positional args and flags; access as usage_<name> in run scripts
• Use sources and outputs to enable incremental caching and avoid unnecessary runs
• Use hidden tasks for internal checks (credentials, tokens) and expose only user-facing tasks
• Prefer runtime-native watchers when available; use mise watch only for runtimes lacking watchers
• Declare task-specific tools and dir to isolate environment and reproducibility

Example use cases

• Create a CI task that depends on lint, test, and build and posts coverage-report after success
• Define a deploy task with depends_post notify and a confirm prompt to protect destructive operations
• Add a release task that verifies GH_TOKEN via a hidden helper before running semantic-release
• Set up deploy usage arguments (environment, force, region) and read them as usage_environment/usage_force
• Configure build sources/outputs to skip recompilation when artifacts are up-to-date