Verify a code change
verify_changeHave Veridu review a code change you just made, before you commit or open a pull request. Independent reviewers check the change against the files you send (for PHP, Veridu also traces callers and overrides within them), findings that cannot be grounded in the code are dropped, and only problems both reviewers confirm can block. You get an outcome (pass / review / block) and concrete findings with file, line, severity and evidence.
Send: diff = git diff --no-renames <base> of your change (include new files: git add -N first),
and files = the FULL current content of every file the diff adds or modifies, keyed by repo-relative path.
You may add up to a few closely related unchanged files (callers, interfaces) to files for context.
Text files only; no renames, mode changes, symlinks, submodules or binaries. Limits: diff 256 KB / 60 files,
files 512 KB total.
After fixing findings, call again with the new diff. Veridu links it to the previous check of the same files
(last 24 hours) automatically; pass parent_change = an earlier change_id only to link a different one.
Up to two follow-ups per change do not count as a new review. Sending exactly the same change again returns the earlier result.
Every finding has a finding_id that stays the same across follow-ups while the problem persists. A follow-up also
returns followup: which ids persist, which came back (reported earlier in the chain, skipped last time), which are new
(possibly introduced by your fix), and which are no longer reported,
with code_changed saying whether the flagged line changed. "No longer reported" is not proof of a fix.
Low-severity findings can be left out of the list but are still counted in followup. An identical resend returns the earlier result as it was.
Each other new change counts as one review on the signed-in Veridu account.
Results are advisory: Veridu sees only what you send, not the rest of the repository. If the review is still running after ~45 seconds you get a change_id and stage_label (what Veridu is doing now): tell the user that line, then call get_change with the change_id (do not call verify_change again for the same change).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| diff | Yes | Unified git diff of the change (git diff --no-renames). | |
| files | Yes | Repo-relative path → full current file content, for every added/modified file (+ optional related files). | |
| intent | No | One or two sentences: what the change is meant to do. | |
| repo_name | No | Optional label, e.g. owner/repo. | |
| parent_change | No | Optional. Veridu links a follow-up to the previous check of the same files automatically; pass a change_id to link a different check, or "none" to start a fresh one. |