17 -Run `mise tasks --all` to list root and extension-local tasks.
18 -Use monorepo-root paths when referring to tasks from automation or documentation:
20 -- `//:test` addresses a root task.
21 -- `//extensions/angel:test` addresses an extension task.
22 -- `//extensions/...:bench` selects a task across matching extension config roots.
24 -Task-name groups and wildcards select tasks; they do not create dependencies or ordering.
25 -Use `mise task info <task>` for task details, `mise tasks deps <task>` for declared dependency edges, and `mise run --dry-run <task>` to inspect execution.
26 -Run `mise tasks validate` after changing the root config.
27 -Run `mise -C extensions/<name> tasks validate` after changing an extension config.
33 -| Install exact locked dependencies | `mise run //:install` |
34 -| Regenerate `package-lock.json` | `mise run //:lock` |
35 -| Format the repository | `mise run //:fmt` |
36 -| Verify repository formatting and lint | `mise run //:lint` |
37 -| Run the complete test suite once | `mise run //:test` |
38 -| Run one extension's tests | `mise run //extensions/<name>:test` |
39 -| Lint one extension | `mise run //extensions/<name>:lint` |
40 -| Typecheck and statically check one extension | `mise run //extensions/<name>:check` |
41 -| Typecheck and statically check all extensions | `mise run //:check` |
42 -| Run property tests | `mise run //:fuzz` |
43 -| Run all benchmarks sequentially | `mise run //:bench` |
44 -| Run all browser E2E suites | `mise run //:e2e` |
45 -| Run the release gate | `mise run //:ci` |
47 -Use `mise run //:test -- extensions/<name>` and `mise run //:build -- <name>` only when implementing a local task or diagnosing its root delegate.
48 -Normal agent workflows should use the extension-local task names.
50 -Root operation tasks are `//:list`, `//:changelog`, `//:readme`, `//:demo`, `//:release-plan`, `//:release-prepare`, and `//:publish`.
51 -Invoke one with `mise run`, passing extension names after `--`, for example `mise run //:readme -- angel`.
17 +Run `mise tasks --all` to list tasks.
18 +Use monorepo-root task addresses: `//:<task>` or `//extensions/<name>:<task>`.
19 +Use extension-local tasks for one extension; root tasks for repository-wide checks.
20 +Before selecting unfamiliar tasks, editing Mise configuration, or managing hooks, read [docs/automation.md](docs/automation.md).
53 22 ##
Efficient execution 57 26 - During iteration, use one extension's local `lint`, `test`, or `check` task.
58 27 - For complete tests, run root `//:test` once; do not fan out all extension `test` wrappers into one Vitest process per extension.
59 28 - For complete static validation, run root `//:check` once; do not fan out all extension `check` wrappers because each repeats repository-wide TypeScript checking.
60 -- Before pushing, run `mise run //:ci`.
62 30 Mise task jobs and tool workers multiply.
63 31 Set `--jobs` deliberately when invoking multiple independent tasks, because Vitest, Playwright, and other tools manage their own workers.
64 32 Use `:::` only for independent ad hoc tasks that should run concurrently.
68 -Use `depends` for prerequisites so Mise can deduplicate shared work and schedule independent dependencies concurrently.
69 -Use structured task references instead of spawning nested Mise processes:
72 -run = [{ task = "//:test", args = ["extensions/angel"] }]
75 -A `run` array is sequential.
76 -Use `{ tasks = ["check", "lint"] }` for an explicit parallel stage inside that sequence.
77 -Structured task references execute their own dependencies but do not appear as edges in `mise tasks deps`.
78 -Use a nested `mise run` command only when a required CLI scheduler option, such as `--jobs 1`, has no structured-task equivalent.
80 -Do not set `raw = true` unless a task requires stdin.
81 -Raw tasks serialize against other tasks and disable output redaction.
85 36 Luci at `ci.bugabinga.net` auto-discovers `.ci/*.kdl` from the public Soft Serve repository.
91 42 ##
Extension engineering 44 +- Nested model calls must use `ctx.modelRegistry`, never pi-ai compatibility dispatchers, so extension-registered providers work.
93 46 ###
Startup performance 95 48 - Treat every Win32 process spawn as expensive.
129 82 - `pre-commit` runs format, lint, and test.
130 83 - `pre-push` runs full CI.
132 -Hooks are managed through `mise generate git-pre-commit`.
133 -Reinstall them with `mise generate git-pre-commit --write`, then `mise generate git-pre-commit --hook pre-push --task pre-push --write`.
135 85 ##
Troubleshooting 137 87 Run `mise doctor` when a task fails because a command is unavailable.