- Industry
- IT Company
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Decision-maker
- Approver
- Engineering Manager
- Code
- ENG-04
It reviews pull requests on client and SaaS repositories for bugs, security flaws, tenant-isolation risks, missing tests, open-source licence problems and breaches of the coding standards, commenting on exact lines. It decides whether to approve, request changes or block, and enforces each client's own review rules where the contract sets them.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the source code repository and CI/CD: the pull request, its diff, CI results and the repository's review rules..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Engineering Manager with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the source code repository and CI/CD: it posts the review comments and sets the review decision on the pull request. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The code review standard: coding standards per language, the secure coding checklist, sensitive paths, client-specific review requirements, and the licence policy.
Reads from
the source code repository and CI/CD: the pull request, its diff, CI results and the repository's review rules.
Acts in
the source code repository and CI/CD: it posts the review comments and sets the review decision on the pull request.
Hands back
An object with decision (approve, request_changes or block), comments (a list with path, line, severity and comment), licence_flags (a list) and summary.
Asks a person when
The change touches auth/, tenancy/, billing/, migrations/, infra/, crypto/, adds a dependency outside the licence policy, or the decision is to block.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Block on findings of | high | A finding at or above this blocks the merge. |
| Largest reviewable change (lines) | 400 | Larger changes are asked to be split. |
| Tests required | On | When on, behaviour changes without tests are not approved. |
| Sensitive paths | auth/, tenancy/, billing/, migrations/, infra/, crypto/ | Comma-separated paths that also need a human reviewer. |
| Most comments | 15 | The review keeps to the most important comments. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Block the merge on any finding at or above high, including any cross-tenant data access.
- Ask for changes over 400 lines to be split.
- When on is true, behaviour changes without tests are not approved.
- Changes under auth/, tenancy/, billing/, migrations/, infra/, crypto/ also need the Engineering Manager.
- Flag any new dependency whose licence is not on the licence policy, and any secret in the diff.
- Keep to 15 comments on the exact lines, most severe first.
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.