Veridu
Change impact

How to find what a code change breaks before you merge.

Most breakage from a reasonable-looking change happens outside the diff: in a caller, a subclass or a doc page nobody opened. Here is what to check, and which of it Veridu checks for you.

Try it freeSee a full review
The checklist
  1. 1
    Callers of anything whose signature or behaviour changed. Search for the function or method name across the repository, including places it is called by string, from templates or from config.
  2. 2
    Subclasses that override what you now call or changed. Search for classes that extend the one you touched, and read their versions of the method.
  3. 3
    Implementations of a changed interface or abstract method. Every class that implements it has to fit the new contract.
  4. 4
    References to code you removed or renamed. Search for the old name everywhere: code, tests, templates, config, docs.
  5. 5
    Documented behaviour and defaults. If a default or an error changed, check the docs and anything that relies on the old behaviour.
  6. 6
    The same bug in other places. A fix applied where you were looking often leaves the identical code unfixed in a sibling file.
What Veridu checks, by language
PHP
Callers, subclasses, implementations and references to removed code are traced before review and handed to the reviewers.
TypeScript, JavaScript, Python
Veridu detects changed definitions, and code a fix left unchanged elsewhere, and fetches the code that uses them.
Everything else
Other code and configuration, including YAML, Ansible, Terraform and Dockerfiles, goes to agent reviewers that read and search the checkout themselves. Documentation, plain text and assets on their own do not.

The reviewers then check the change in that context. Two real examples, from Laravel and Fastify: pull request impact analysis.

Questions
Is this a call graph?

No. It is a bounded text search, capped so a large repository cannot flood the review. It can miss dynamic calls, and it does not follow framework indirection such as Laravel facades, container bindings or event listeners.

Does it work before I commit?

Yes, through verify_change from Claude Code, Codex or another MCP client. There Veridu sees only the files the agent sends, so it traces callers and overrides (PHP) within those files, not across the whole repository. The pull request review searches the whole checkout.

Will it find everything?

No. It finds more of what a diff-only review misses, and it says when a review could not see all of the changed code. Use the checklist above for anything it cannot reach.

What does it cost?

Up to 20 reviews a month on public GitHub repositories are free, no card. Solo and Team plans add private repositories.

Check your next change

Before the commit from your agent (Claude Code, Codex), or on the pull request (how PR reviews work).

Try it freeRead the docs