on-task-done
Task-completion flow: `/cr` (a `/code-review` answered with `/code-review-response`, which ends with `/distill`), update docs (spec/cheatsheet/compiler/optimizer), then run `mise run on-task-done` (bu
SKILL.md.claude/skills/on-task-done/SKILL.md
GitHubOverview
First, review the branch with /cr: a review answered with
/code-review-response, which ends with /distill.
Then update docs if applicable:
- docs/spec-*.md
- docs/cheatsheet.md
- docs/compiler.md and docs/optimizer.md, only when what they map changes: a phase, pass, or IR, or a rule that holds across phases. How one works belongs in its module doc.
Then, run time mise run on-task-done, which includes:
cargo build
mise run clippy-fix
mise run update-golden-fixtures
mise run update-golden-format-fixtures
mise run doc-stdlib
mise run format
mise run test
mise run test-wado
mise run check
mise run check-grammar
mise run check-highlight
on-task-done is the longest task there is.
Notes
- Don't pipe it into
tail— you lose the full log. Redirect to a file and inspect it afterwards if you need to trim output. - The changes generated by the command are necessary. Commit them.
- Run it in the background and read the log when it lands.
- If the changes only include Wado programs, only
mise run test-wadois required. - If the changes only include documentation, only
mise run formatandmise run checkare required.
Flaky Commands
Some commands are flaky and may segfault:
mise run update-golden-fixtures— thegolden-dumpbatch tool sometimes segfaults mid-run (pre-existing issue). If it fails, run the individual golden generation manually for any new fixtures, then proceed.mise run test-e2e(i.e.,cargo test --workspace --test e2e) — the e2e test runner sometimes crashes with SIGSEGV when running all tests in parallel (pre-existing issue unrelated to compiler correctness).
If cargo test segfaults, reduce parallelism:
cargo test --workspace --test e2e -- --test-threads=4
Or run individual fixture tests directly:
cargo test --workspace --test e2e -- <fixture_name>