check_done
Am I done? The stop condition for a coding loop. Free — no subscription, no token budget, no rate limit.
Composes what verifAIed already knows about a branch — failing tests plus the coverage of the functions you changed — into a single verdict you can gate on:
done(bool):trueonly when there are no gaps at all. This is the strict signal to stop.status:"done"|"done-with-warnings"|"not-done".done-with-warningsmeans the only remaining gaps are ones the repo owner marked non-blocking — read this yourself if you want to stop early.scope:"changed-functions"when a default-branch base exists (only added/modified functions are judged), else"all-functions".gaps: each remaining problem with aref, the id to act on (function_id/test_id), and anext_actionpointing atget_baseline_prompt(free) orfix_branch(paid). Gap kinds:failing_test— a test that failed or errored.untested_function/partial_function— a changed function with no coverage, or only some.unexercised_browser— a changed function that no browser reached, in either the browser-coverage or the manual dimension. Only judged once one of them exists.visually_unreviewed— a changed component nobody has looked at.intent_mismatch— somebody looked and it didn't do what the change claimed. Both only judged once the branch has at least oneverify_uiverdict.unverified_recorded_test— a recorded test this branch has never run, or whose last run failed. Re-run it withverifaied test run "<feature path>/<name>"— the feature path is optional and may nest. Branch-wide, not diff-scoped. Absent entirely for a repo with no recorded tests.visual_defect— somethingverifaied auditmeasured in the rendered page (overflow, contrast, a broken image, a console error), from the most recent audit of the branch. The one kind that is a warning by default, so it routes todone-with-warningsrather than blocking unless the repo owner turned it on. Only judged once the branch has been audited at least once.
Gaps are ordered so a component's own gaps are immediately followed by its handlers' and render branches'; a sub-unit gap carries
parent_ref(the parent'sfile::Name) so you can group or indent them without parsing refs. The clustering is presentation only — every gap is still individually actionable by its ownref/function_id.not_checked: signals that couldn't be evaluated (e.g. failing tests when no junit.xml was uploaded, orunexercised_browserwhen functions exist but no browser coverage was uploaded) — surfaced so a green verdict is never silently green.
Pagination: gaps is capped at max_gaps per call (default 50) to
stay within tool-result limits — a low-coverage branch can have hundreds.
done, status, scope and gaps_total ALWAYS reflect the full
gap set, never just the returned page, so a truncated page is never
mistaken for a clean branch. When more gaps remain, has_more is
true, next_offset is the offset to pass next, and note spells
out how to fetch the rest — call again with that offset until
has_more is false.
The intended loop: run your tests with coverage (pytest → coverage.json,
or vitest run --coverage --coverage.provider=istanbul →
coverage/coverage-final.json) → upload_local_coverage →
check_done → fix each gap (get_baseline_prompt / fix_branch)
→ re-upload → repeat until done is true.
repository is the GitHub 'owner/repo' (a repo UUID also works);
branch defaults to the repository's default branch. Errors with an
actionable message when no analysis exists for the branch yet — upload
coverage first.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"repository": "<repository>"
},
"name": "check_done"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| branch | No | ||
| offset | No | ||
| max_gaps | No | ||
| repository | Yes |