GitHub App

How do I get an automatic review on every GitHub pull request?

Install the Veridu GitHub App and link the repository on veridu.io. Each pull request is then reviewed when it is opened ready or marked ready for review, and the findings are posted as a PR comment and a Veridu check. Bot pull requests are skipped.

How to set it up
  1. 1
    Install the Veridu GitHub App. Install it on GitHub.
  2. 2
    Link each repository on veridu.io. Link it on the Repos page. Repositories added to the installation later need linking too. Until a repository is linked, its pull requests show a neutral "Veridu setup" check with a link to finish.
  3. 3
    Open a pull request ready for review. Veridu reviews it automatically when it is opened or reopened ready, or marked ready for review. Findings post as a PR comment and a Veridu check.
When a pull request is reviewed
Ready for review
Reviewed once, automatically, when it is opened or reopened ready, or marked ready.
Drafts
Not reviewed, unless the repository has "Review before a human" turned on. That optional mode reviews every push to a draft.
New commits
Not reviewed automatically. The check changes to a neutral "New commits not reviewed". Comment /veridu review on the pull request to review the current commit; owners, members and collaborators can use it, up to 20 times a day per account.
Bot pull requests
Pull requests from bots such as Dependabot and Renovate are skipped.

More on the draft mode: review before a human.

What blocks, and what is shown
  • What blocks. A review blocks only when two reviewers find the same defect independently and both rate it at or above your blocking threshold. A failing Veridu check stops a merge only if you make it a required check.
  • What is shown. Other findings are left for the human reviewer. Findings below the repository's display level (medium by default) can be left out of the PR comment, with a link to the full review. Findings that cite a file or line that does not exist are dropped.
  • What it could not see. If some changed code was not reviewed (files marked generated, vendored or minified, or a diff too large to review in full), the review is marked incomplete. Incomplete reads as review, never pass.

How Veridu decides what can block: cutting AI code review false positives. What it checks outside the diff: pull request impact analysis.

Questions
Does it review every push?

No. A pull request is reviewed when it is opened or reopened ready, or marked ready for review. New commits are not reviewed automatically; comment /veridu review to review the current commit. With "Review before a human" turned on, Veridu reviews every push to a draft.

Does it approve pull requests?

Never automatically, and never as the GitHub App. It reports what it checked and what it found. A person still decides.

Does it look outside the diff?

Yes. Each review checks the pull request against the code it affects outside the diff. Callers, subclasses and implementations are traced before review for PHP; other languages get less, as described on the change impact page.

Do I need an AI subscription?

No. GitHub App pull request reviews need no AI subscription. Veridu's reviewers run on Veridu's own OpenAI and Anthropic API access.

Does it work on private repositories?

On a paid plan. The free tier includes up to 20 reviews a month on public GitHub repositories, no card. Solo and Team plans add private repositories.

Review your next pull request

Free for public repositories, up to 20 reviews a month. See pricing for private repositories. To catch problems before the pull request, your agent can check its own change first: Claude Code, Codex, Cursor.