AI pull request review

Every pull request reviewed as it opens. Real scanners, then AI, then a judge.

Works with GitHub and GitLab.

acme/Retry failed charges

Retry failed charges #214

Completedacme/web· started 2m ago
SummaryFindings3Finishing touches
All 3Critical 0Major 1Minor 2
Posted as inline comments 1
Add an idempotency key to the charge retryMajor severity

Evidencecharge.ts · L42–L43

SUGGESTION

stripe.charges.create(toCharge(order), {
  idempotencyKey: `charge-${order.id}`,
})
correctnessconfidence 0%
JUDGE keep — a network timeout is enough to double-charge.
Show 2 findings filtered out by the judge

Fast code. Faster reviews.

Coding agents open more pull requests, and bigger ones, than any team can read line by line. HootPR reads every one the moment it opens.

01 Review

AI code reviews that catch what matters.

Linters, scanners and a code graph feed specialist reviewers, then a separate judge drops the noise. What reaches your PR is worth reading.

02 Walkthrough

Understand every PR at a glance.

Every pull request and merge request gets a walkthrough comment, so reviewers know what changed and why before they open a single file.

03 Change Stack

Review massive diffs layer by layer.

Change Stack regroups a large PR into ordered layers, from data model to UI, so you review the story of the change instead of an alphabetical file list.

04 Security

Security review on every change.

Scanners run in a sealed sandbox on every PR, and attack surface maps and security reviews show your posture across repositories.

How HootPR thinks

Context before comments.

Every review is assembled in stages. Tools gather facts, the graph adds reach, your rules add taste, and a judge keeps only what holds up.

Beyond the review

More ways to ship with confidence.

The same context that powers each review answers questions, writes the boring parts and keeps the whole team in the loop.

Chat with @hootpr in the PR

Mention @hootpr on any finding to ask why, push back or get a fix. It answers in the same thread, and what you teach it becomes a learning for that repository.

Pre-merge checks

Title, description, docstring coverage and linked issues, plus your own checks in plain English. Run them as warnings or as errors that fail the HootPR status.

Finishing touches

Comment “generate docstrings” or “generate unit tests”. HootPR writes them in a sandbox, runs your tests and opens a stacked PR.

Reports by email

Ask for any summary of your review data, or schedule a daily, weekly or monthly digest by email.

Dashboard analytics

Reviews, findings, acceptance rate and time to first review, broken down by repository and author.

Credits you can audit

Every hold, charge, refund and credit pack is a line in your organization’s ledger. New organizations start with free credits.

How it works

From sign-in to first review in minutes.

  1. 1

    Sign in

    With GitHub or GitLab.

  2. 2

    Install on your repos

    Pick the repositories or projects HootPR may read.

  3. 3

    Open a pull request

    Reviews start on open and on every new commit.

  4. 4

    Read the walkthrough

    A summary comment, inline findings and a HootPR check.

Get started with HootPR

Get started