wado-lang/wado / .claude/skills/on-task-done
on-task-done
VerifiedTask-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.
Overview
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>
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |