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` (build, clippy-fix, golden + format fixtures, doc-stdlib, format, tests; the longest task there is) and commit its generated changes. Invoke ONLY when the user asks for it by name or explicitly asks to run the completion flow — never on your own initiative, and not because a task looks finished.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
First, review the branch with /cr: a review answered with
/code-review-response, which ends with /distill.
Then update docs if applicable:
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.
tail — you lose the full log. Redirect to a file and inspect it afterwards if you need to trim output.mise run test-wado is required.mise run format and mise run check are required.Some commands are flaky and may segfault:
mise run update-golden-fixtures — the golden-dump batch 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 (i.e., cargo test -p wado-compiler-tests --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 -p wado-compiler-tests --test e2e -- --test-threads=4
Or run individual fixture tests directly:
cargo test -p wado-compiler-tests --test e2e -- <fixture_name>
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Measure Wado's performance or the size of the Wasm it generates, and refresh the benchmark/ and wasm-size/ README files. Use for any benchmarking or size-measurement request, whichever benchmark it names.
The English summary is being prepared. Showing the original description.
Measure how long GitHub Actions jobs and steps took across past runs, and find the pull request that made CI slower. Use for any question about CI duration, a slow job, or when CI got slow.
The English summary is being prepared. Showing the original description.
How to answer code review feedback — a human reviewer, CodeRabbit, or any review bot. Verify the findings, report the classes they are instances of to the user before fixing, then fix the class rather than the sites named. Put design decisions to the user, then run /distill. Invoke when responding to review comments on a pull request, or to the findings of a /code-review run.
The English summary is being prepared. Showing the original description.
Investigate and improve code coverage for the wado-compiler crate. Use for any question about what the tests do and do not reach, dead code included.
The English summary is being prepared. Showing the original description.
Review the branch with /code-review at high, then answer the findings with /code-review-response.
The English summary is being prepared. Showing the original description.
Use rust-gdb to inspect variables and step through code without modifying it. Prefer it over print debugging for any investigation into what the compiler is actually doing (lldb is unavailable on Claude Code Web).
The English summary is being prepared. Showing the original description.