scaffold

# mise:scaffold — Scaffold the mise config & task library Create the `MISE_ENV`-selected mise config under **`.config/`** for the target repo, following the `mise` skill's standard. Default the target to the current repo root; if `$ARGUMENTS` names a directory, scaffold into `<dir>/.config/`. ## 1. Detect, then confirm Inspect the target for the language runtime and tooling before writing: - **Node** — `package.json`, `pnpm-workspace.yaml`, `pnpm-lock.yaml` - **Python** — `pyproject.toml`, `uv.lock`, `requirements.txt` - **Flutter/Dart** — `pubspec.yaml` - Existing `dprint.json`, `.pre-commit-config.yaml`, `taplo.toml`, `gitleaks.toml` → those tools belong in `mise.dev.toml` Then ask the user, in one batched round, only what you cannot infer: 1. **Will this repo be built/deployed through CI/CD?** If no, scaffold `mise.toml` alone and stop — variants are added when a pipeline appears. 2. **Which runtime env vars differ between local and production?** (e.g. `LOG_LEVEL`, `RUNTIME_ENV`, service endpoints) — so the dev/ci values split. 3. Confirm the detected runtime and dev tooling. Do not invent project-specific env vars. If the user names none, leave the `[env]` override sections with just the common keys. ## 2. Write the files Follow the `mise` skill exactly. Key rules: - `mise.toml` — shared `[settings]`, **runtime `[tools]` only**, common `[env]` (`DISABLE_TELEMETRY`), and **`[tasks.init]`** (the task-chmod bootstrap lives in the base so tasks run under...