Verification
Generation is not completion. A task is reviewable when the relevant test, type check, linter, or build has run and its result is visible.
On this page
01
Prefer the narrowest useful check
A focused unit test is usually a better first signal than a full workspace build. Expand verification when the changed boundary or repository instructions require it.
02
Require a finish verifier
Use finish verification for automation or whenever the task should not report completion without a specific command passing.
Command
buildstax --verify-on-finish --finish-verifier-command "npm test" "Fix the failing validation test."03
Keep failures in the result
A failed check is useful context, not something to hide. The final result should distinguish checks that passed, checks that failed, and checks that could not run.