Run NeoHaskell doctest examples, all local Cabal test targets, or the maintained Hurl testbed when a framework change needs runtime verification.
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.
Use the owned scripts for broad runtime checks. They enter the shared project toolchain, keep transcripts under .agents-state/neohaskell-test/, and report unavailable checks as SKIP. Add --strict when every discovered target must run. Each child command has a timeout and an 8 MiB output limit. A host fallback is labelled as unpinned.
scripts/run-doctest. The script discovers local packages through cabal.project and their source settings through each Cabal file.scripts/run-full-suite. Cabal receives the all target, and the script checks results against test-suite components declared by the project. It then runs the maintained Hurl testbed when Hurl and PostgreSQL are ready.scripts/run-testbed. PostgreSQL must already be available. The owned entrypoint delegates application startup and teardown to testbed/scripts/run-tests.sh. It does not install Hurl or start PostgreSQL.These commands exercise the local development build. Use optimized-build, generated-consumer, cross-platform, or CI checks when those contracts matter. The owned scripts run no lint or formatter checks.
Framework export, TH marker and generated-API changes also require NeoHaskell consumer verification. Review its starter and testbed migration requirements and run the generated-project contract alongside the affected testbed checks. A passing framework suite does not replace those consumer checks.
For workflow path selection and draft full-CI opt-in, see CI verification.
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.
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.
The English summary is being prepared. Showing the original description.
Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.
The English summary is being prepared. Showing the original description.
Inspect or supervise a PR or stack through review and CI to merge-ready, using current GitHub evidence and the requested mode.
The English summary is being prepared. Showing the original description.
Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you benchmark or report a measured speedup or regression, including complete framework flows and compilation of projects that consume the framework.
The English summary is being prepared. Showing the original description.
Restate the last message in plain human language, with no jargon.
The English summary is being prepared. Showing the original description.
Build or adapt a local harness to drive, inspect, and profile an interactive CLI or TUI without external services. Use for CLI UX checks, startup regressions, memory leaks, hangs, prompt flows, or terminal demos.
The English summary is being prepared. Showing the original description.