kumiko check

kumiko check

Runs the same quality gates CI runs, in parallel where possible. The typical wall-clock is 60-120 seconds on a warm cache.

What it runs

Step	Tool
Lint	Biome
Types	`tsc --noEmit` (every package)
Guards	the 14 multi-repo guards in `infra/guards/`
Tests	`bun test` (unit + integration)

The four steps run in parallel; tee’d logs land under /tmp/kumiko-check-*.

Parallel-lock

Concurrent invocations of kumiko check don’t compete, the second call detects the running one via lockfile and tails its output. Lead crashes release the lock atomically.

This makes it safe to call kumiko check from a pre-push hook and from a foreground terminal at the same time.

Scoping

Set KUMIKO_CLI_SCOPE to one of framework, enterprise, platform, studio, publicstatus to limit the check to a single repo:

KUMIKO_CLI_SCOPE=framework kumiko check

This is what the pre-push hook does, it scopes to the repo the push is coming from instead of running all five Kumiko repos.

When to use

Before opening a PR
After resolving merge conflicts (catches lint regressions instantly)
When CI fails and you want to reproduce locally

When NOT to use

Pre-commit. Use kumiko check:fast, it runs the same scope but only against changed files.