Review Before Merge
Reads a change the way a careful colleague would, before anybody is asked to approve it.
A review that arrives three hours late has already cost more than it saved, and a reviewer who opens fourteen files at five in the afternoon reads the first four properly. The concept reads all of them against the standards the team agreed, names what it found with a file and a line against each, and says plainly which files it had nothing to say about. It would post nothing until asked, because a review comment is a thing somebody then has to answer. None of it is built yet.
Availability
In Development. Specified, and not built. The run below is the shape the job would take, not a recording of one. Nothing of it runs today, so it cannot be subscribed to and carries no price.
Intended user
A developer waiting on a review, and the reviewer who has fourteen files to read at five in the afternoon.
Monthly price
Not purchasable. No price, and no subscribe button until it runs.
Nothing here runs yet, so there is no Subscribe and no Run on this page. Asking for it is what decides which of the five gets built first, and a close variation of it can be quoted as a custom build today.
What this is not.
The corrections worth making before anything else on this page is read, because each one is a thing a reader could reasonably assume and would be wrong about.
- Not a security audit. A first read is not an assurance exercise, and a draft with nothing in it is not a statement that a change is safe to ship.
- It never merges and it never posts on its own. Drafting is the end of what it would do by itself.
- What it reads against is yours and stays yours. How it weighs a finding is ours and is not published — a public page is the wrong place to look for the review rubric, and it is not in this site's markup, data or structured output either.
How the job would go.
Four steps, in order, ending where it stops. No timing is published for any of them: nothing has run, so there is nothing to measure, and a written duration shown as a measurement would be an invention.
Review Before Merge, start to finish
Illustrative- Reads every changed file in the diff
- Checks each against your written standards
- Notes each finding with its file and line
- Drafts the review and waits
Illustrative. The steps are written for this page to show the shape of the job, and none of it is a recording.
What would land when it finishes.
A drafted review naming each finding with the file and the line it belongs to, and naming the files it had nothing to say about.
| File | Line | What it found |
|---|---|---|
| orders/repository.ts | 142 | A query built by joining strings |
| orders/service.ts | 88 | The refund path has no test |
| orders/types.ts | 20 | A name the house style spells differently |
The other 11 files would be named in the draft as having nothing against them. The filenames and the findings are written for this page.
Illustrative. These rows are written for this page and are never a customer’s data.
Supported inputs
Kinds of source, from accounts you would connect in your own Tools workspace. Which account, and the credential behind it, are yours and never appear anywhere on this site. No named integration is listed, because none has been built.
- The diff
- Your written standards
- Test history
Output
A drafted review naming each finding with the file and the line it belongs to, and naming the files it had nothing to say about.
IllustrativeApproval boundary
Post the review?
Reading, checking and comparing change nothing outside your workspace and would happen on their own. Anything that cannot be taken back waits for you, and what it is asking about is shown in full rather than summarised.
Review Before Merge is in development.
It is specified and not built. Billing does not exist yet and the usage allowance has not been measured, so there is nothing to subscribe to and no price to show. Asking for it is what decides what gets built next; a close variation of it can be quoted as a custom build today, against acceptance cases you write.
The rest of the catalogue.
- Invoice MatchingFinanceChecks every invoice against the order it came from and the goods that actually arrived.
- Month-End CloseFinanceClears the accounts that reconcile at month end and writes the first draft of the close narrative.
- Incident TriageEngineeringTurns a night of alerts into a short list of grouped incidents, each with somewhere to look first.
- Idle Cloud SpendEngineeringFlags cloud resources with no recorded activity, works out who owns each one, and estimates what stopping it would save.