A command that runs the complete verification gate and refuses to call work done until every check is green. It reports exact pass counts per gate so "done" means something.
---
description: Before considering work done, run typecheck, lint, unit tests, api-flow (e2e), and build; fix all errors and ensure everything passes 100%.
---
Run the full verification gate and report results.
Steps:
1. Run typecheck, lint, unit tests, api-flow (e2e), and build.
2. Fix every error until all gates pass 100%.
3. Report exact pass counts per gate: `typecheck 0 errors | unit X pass | api-flow Y pass | e2e Z pass | build ok`.
4. Only declare done when fully green; if anything fails, fix and re-run, don't stop to ask.Green or not done#
Step 4 is the rule that matters: a partial pass is a failure. If a gate fails, the agent fixes it and re-runs rather than pausing to ask whether it's good enough.
Report the counts#
A line like typecheck 0 errors | unit X pass | build ok is the difference between a claim and a proof. The exact per-gate counts make the verification auditable at a glance.
The important failure mode#
The dangerous phrase is "tests mostly pass." A repo is either in a verified state or it is not. If a gate is flaky, missing, or too slow to run, the report should say that plainly and explain what was checked instead.
This command also keeps the agent from stopping at the first green-looking signal. Typecheck can pass while build fails. Unit tests can pass while generated artifacts drift. The gate should match the repo, not the agent's patience.