Definition of done

verifAIed decides whether a branch is finished from what was uploaded for it. Your agent asks, gets a list of gaps, and stops only when the answer is done.

Ask whether a branch is done

Upload first: the answer is worked out from the last upload. Then ask from a terminal:

verifaied check-done

An agent connected over MCP calls the check_done tool instead. Both give the same answer. Two options change what the command prints and when it passes:

  • --json prints the full answer as JSON instead of a summary.
  • --allow-warnings lets the command pass when only warnings are left.

Read the answer

The answer is one of three:

  • done: nothing is left.
  • done-with-warnings: the only gaps left are ones your repository treats as warnings.
  • not-done: at least one blocking gap is left.

Each gap says what is wrong and where, whether it blocks, and the next action that closes it: a prompt for an untested function, a test to run again, a page to check again.

The answer also lists what could not be checked. For example, if no junit.xml was uploaded, failing tests are listed as not checked. Read that list: a branch can be done while something on it was never looked at.

When the branch can be compared with your default branch, functions are judged only if the branch changed them. Otherwise every function is judged.

The eight switches

Eight kinds of gap can block a branch. Each has a switch under Settings → Definition of done on the repository's page. Change the switches, then click Save.

SwitchWhat it meansStarts as
Failing testsA failed or errored test blocks done.On (blocks done)
Untested functionsA changed function with no tests blocks done.On (blocks done)
Partially covered functionsA changed function only partly covered blocks done.On (blocks done)
Unexercised in browserA changed function no browser session exercised (frontend or backend) blocks done.On (blocks done)
Visually unreviewedA changed component with no verify_ui verdict blocks done. Only applies once this branch has at least one verdict.On (blocks done)
Intent mismatchA verify_ui check that came back failed blocks done until the UI matches what it was supposed to do.On (blocks done)
Unverified recorded testsA recorded test this branch has never run — or whose last run failed — blocks done. Only applies once the repo has recorded one.On (blocks done)
Visual defectsOff by default — the only signal that starts as a warning. verifaied audit measures a rendered page without knowing which of your choices were deliberate, so findings are reported but don't block until you turn this on.Off (warning only)

A switch that is on makes its gaps blocking. A switch that is off does not hide anything: its gaps are still reported, as warnings, and they do not stop the branch from being done.

Good to know

  • Unverified recorded tests looks at every recorded test on the branch, not only the ones near your change. A change that did not touch a screen can still break it. The switch has no effect until the repository has a recorded test.
  • Visually unreviewed applies only once the branch has at least one visual verdict. A branch that never used visual checks is not held to them.
  • Visual defects is the only switch that starts off. An audit measures the page without knowing which choices you made on purpose, so its findings are warnings until you turn the switch on.

What browser tests are, Code reached and Visual checks explain where those gaps come from.

Exit codes

CodeMeaningWhat to do
0Done.Stop.
3Blocking gaps remain.Fix every gap that was printed, upload and ask again.
2API error, such as a rejected token, no upload for the branch yet, or no network.Fix the connection. Do not treat it as done.
1Usage error, such as no token, a repository name that cannot be used, or a repository that is not connected to your account.Fix the command.

The command is strict by default: done-with-warnings also exits with 3. Add --allow-warnings to make it exit with 0.

Use it as a CI gate

Because the exit code is the answer, the command works as a step in a CI job. Give the job a token as the VERIFAIED_API_TOKEN secret, upload the coverage with verifaied upload, then run:

verifaied check-done --allow-warnings

The job fails while blocking gaps remain. Leave out --allow-warnings to fail on warnings too. CI coverage covers the upload.