Get client pull requests to senior review in better shape.
Developers check each change with Veridu before asking for review. It looks at the code the change affects, not just the diff, so your senior engineers spend their time on what a person needs to judge.
- Senior engineers review work across several client projects, often in codebases they do not touch every day.
- Developers move between unfamiliar codebases, and the code a change breaks is usually outside the diff.
- AI coding tools have raised how much code gets written faster than senior review capacity.
- On fixed-price work, every extra review round comes out of the margin, and a defect that reaches the client costs more than the fix.
- 1Before asking for review, the developer's agent checks the change. From Claude Code, Codex or another MCP client, the agent calls verify_change with its diff and the changed files, fixes the findings that hold up and checks again. No repository connection is needed for this step.
- 2On the pull request, Veridu reviews it against the code it affects. With the GitHub App on the client repository, each pull request is reviewed once when it is ready, against the code the change touches outside the diff (for PHP, its callers, subclasses and implementations). Findings post as a PR comment and a check.
- 3The senior engineer starts from what is left. Only problems two reviewers find independently, at or above your blocking threshold, make the Veridu check fail; that stops a merge if you make it a required check. Wrong findings are dismissed with a reason that stays on record. Your engineers still review and approve.
Setup for developers: Claude Code · Codex · pull request reviews. To review every push to a draft before a person looks at it, see review before a human.
Does it work on private client repositories?
Yes. The pre-commit check from the developer's agent works with code from any host and reads only the files the agent sends. The free tier covers checks that are not linked to a repository, and public GitHub repositories. A check linked to a private GitHub repository, and pull request reviews on private repositories, need a Solo or Team plan.
What does it see, and what is kept?
A pull request review checks out the repository into a temporary working directory at the pull request's commit and deletes that copy when the review finishes. The review result and findings can quote lines of code, and are kept until you ask us to delete that review or the whole account; we handle either request within one business day. On some reviews the models' raw responses and the record of what they looked at are kept too, and are deleted automatically after 30 days. For the pre-commit check, the submitted diff and files are deleted 7 days after it finishes; its findings stay with the check. The data handling page has the details, including the GitHub App's permissions.
Data handling →Which AI providers see client code?
OpenAI and Anthropic, through their APIs. Neither uses API traffic for training under their published policies.
We use GitLab or Bitbucket.
Pull request reviews (the App, and veridu review in the CLI) are GitHub only today. The pre-commit check from Claude Code, Codex or another MCP client works wherever the code is hosted.
Which languages does it trace?
Callers, subclasses and implementations are traced for PHP. For TypeScript, JavaScript and Python, Veridu detects changed definitions and code a fix left unchanged elsewhere. Other languages and configuration go to reviewers that search the checkout themselves.
What it checks, by language →Does it replace our technical leads?
No. Veridu never approves a pull request on its own. It gives the reviewer a change that has already been checked, and a list of what was found and dismissed. The account that owns the review can submit its own GitHub approval from the review page, if it has linked a fine-grained personal access token and GitHub allows the approval.
How do we try it?
Pick one client project. Developers add Veridu to their agent and run the check before asking for review; if the repository is on GitHub, add the App for pull request reviews. Your engineers review as normal, so you can compare review rounds before and after. Questions before you start: use the contact page.
Team is $25 per user per month ($20 billed annually, 3 seats minimum), with private repositories and a pooled monthly allowance. See pricing.