UAE · ENBook a demo
Procure AIEngineeringDecision-maker

Code Review Agent

Reviews changes for bugs and standards.

Code Review AgentApplication Engineering
Industry
Procure AI
Department
Engineering
Team
Application Engineering
Kind
Decision-maker
Approver
Tech Lead
Code
ENG-04

It reviews pull requests to the procurement platform for bugs, security flaws, tenant-isolation leaks, money-handling errors, weakened controls and missing tests, comments on the exact lines, and decides whether to approve, request changes or block. It never merges; its verdict is one input to the human reviewer and the branch's merge rules.

How it works

7 steps, and a person signs off before step 7.

  1. 01Looks it up

    Finds the record the request is about in the code repository: the pull request's diff and description, its CI results and the code owners of the files changed..

  2. 02Reads the request

    Works out what is being asked and what a complete answer needs.

  3. 03Checks the facts

    Checks figures, dates and rules against the source records, not from memory.

  4. 04Forecasts, when it decides

    Projects what each option will cost or return before it recommends one.

  5. 05Works it through

    Prepares the draft, match, recommendation or reply, with its sources.

  6. 06Asks a person

    Hands the work to Tech Lead with its reasoning before anything goes out.

  7. 07Acts

    Once approved, it acts in the code repository: it posts the review on the pull request with its line comments and verdict. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The coding standards: language style guides, the review checklist, security and tenant-isolation patterns to reject, money and rounding rules, the list of control code paths (approvals, match, payments, bank details, screening) and code ownership.

Reads from

the code repository: the pull request's diff and description, its CI results and the code owners of the files changed.

Acts in

the code repository: it posts the review on the pull request with its line comments and verdict.

Hands back

An object with verdict (approve, request_changes or block), findings (a list, each with file, line, severity, category (bug, security, tenant_isolation, money, control, test, standard or performance), comment and suggestion), missing_tests (a list), split_suggested (true or false) and summary (one paragraph).

Asks a person when

The verdict is block, the change touches auth/, approvals/, matching/, payments/, supplier_bank/, screening/, migrations/, infra/, or a finding is a security, tenant-isolation or control flaw.

ApproverTech Lead

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Block at this severity or abovehighA finding at or above this severity makes the verdict block.
Largest change reviewed whole (lines)400A larger change is asked to be split, unless generated or a pure rename.
Behaviour changes need testsOnWhen on, changed behaviour without a matching test means request changes.
Paths that need a code ownerauth/, approvals/, matching/, payments/, supplier_bank/, screening/, migrations/, infra/Comma-separated. A change under these needs its code owner as well as this review.
Most line comments per review15It posts at most this many line comments, most serious first.

Limits are settings, not code: a manager changes them without a developer.

Rules it always follows

  • Rate each finding critical, high, medium or low and cite file and line; any finding at or above high makes the verdict block.
  • A query or cache that can return another client tenant's records, or a log line that writes bank details, tax IDs or supplier prices, is critical.
  • Money computed in floating point, a currency dropped from an amount, or rounding that differs from the invoicing rules is high.
  • Never approve a change that adds a secret, weakens an approval, match or segregation-of-duties check, or deletes an existing test.
  • When on is true, changed behaviour without a matching test means request changes; ask for a change over 400 lines to be split.
  • A change under auth/, approvals/, matching/, payments/, supplier_bank/, screening/, migrations/, infra/ needs its code owner and the Tech Lead before the verdict is posted.
  • Post at most 15 line comments, most serious first; style points go in one summary comment.

See the Code Review Agent agent on your own work.

We’ll run it on a sample of your work and show you what your approver would see.

Code Review Agent · Procure AI | Basinwright Industries