mise

Solid

Canonical mise setup — the per-project task vocabulary (install, format, check, test, build, watch) and pinned toolchain that hooks and CI reuse. Use when defining `mise.toml` tasks or pinning tools.

AI & Automation 4 stars 1 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%
23
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Mise Standard Canonical setup for **mise** as the per-project task runner and tool-version manager. One `mise.toml` defines the task vocabulary that git hooks and CI reuse, and pins the toolchain for reproducibility. Mise is the **single source of truth** for what every check does; [lefthook](../lefthook/SKILL.md) and [github-actions](../github-actions/SKILL.md) only decide _when_ to run them. ## Task Vocabulary Every project exposes the same core tasks (with short aliases) so agents, hooks, and CI stay portable. In interactive shells, `mr <task>` is the standard command-line alias used for `mise run <task>`: | Task | Alias | Purpose | | --------- | ----- | ------------------------------------------------------------- | | `install` | `i` | Sync dependencies and install git hooks (`lefthook install`). | | `format` | `f` | Format all sources (fans out to `format:*`). | | `check` | `c` | All static checks in parallel (fans out to `check:*`). | | `test` | `t` | Run the test suite. | | `build` | `b` | Compile or package artifacts (fans out to `build:*`). | | `watch` | `w` | Run the app with live reload (web). | Language stacks ship concrete `mise.toml` files — see [go-stack](../go-stack/references/mise.toml) and [python-stack](../python-stack/references/mise.toml). ## Naming: generic vs specific...

Details

Author
fmind
Repository
fmind/dotfiles
Created
4 months ago
Last Updated
yesterday
Language
Go
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category