16 pull requests to review.
Each one arrives with a ticket and a confident summary of what it does. Read the diff, make the call, and point at the lines. One of these is completely fine — flagging clean code costs you.
The limit that is the load
Five confident comments are already on the pull request. Some are real, some describe code that is not in the file, one is marked a blocker and is not — and the thing that will actually cost money has no comment on it at all. Call each one, then find what nobody said.
No defect to find, and no diff long enough to answer from. You are given a change that is right in isolation and the rest of a system you have never seen, and asked which parts of it disagree. This is the half of review a type checker cannot do and a model given only the diff cannot either.
- 01
The batch that reports success
Every run logs 'sent: 0, failed: 0' and nobody can work out why. The code has a try/catch and everything.
TypeScriptNodeEmailWarm-up— - 02
Retry the charge
Checkout throws a 502 once or twice a day. The agent added retries. Ten lines, very tidy.
TypeScriptNodePaymentsOn-call— - 03
Five per hour
A rate limiter that reads exactly like the docs example. It is not rate limiting, and it is permanently locking people out.
TypeScriptNext.jsRedisOn-call— - 04
Download your invoice
The auth check is right there at the top of the handler. That is the whole trick.
TypeScriptNext.jsAuthOn-call— - 05
Last week in review
Nothing crashes, nothing leaks, nobody gets paged. The numbers are just quietly wrong, and they have been for months.
TypeScriptdate-fnsCronSenior— - 06
Search the projects
Parameterised query, allowlisted sort column, tenant scoping. Three defences, and the agent tells you about all of them.
PythonDjangoPostgresSenior— - 07
Make the dashboard fast
The agent was asked for speed and delivered a cache. The cache works. That is the problem.
TypeScriptNodePostgresSenior— - 08
One line fasterreal · survived 478d
A one-line performance change to a token check. It was reviewed, merged, and wrong for 478 days.
TypeScriptJWTMinedSenior— - 09
Nothing wrong with it
Sixty lines of agent-written React and a reviewer who has been trained to find something. Only one of those is a problem.
TypeScriptReactNext.jsPrincipal— - 10
Normalise the separatorsreal · survived 932d
Sixty lines of path handling from a framework you have probably deployed. One character is missing. It went unnoticed for 932 days.
TypeScriptStatic filesMinedPrincipal— - 11
Joined, not confinedreal · survived 1012dshown in the demo
A file download route, hardened by replacing string concatenation with the platform's path helper. Survived 1012 days.
JavaScriptExpressMinedOn-call— - 12
The limit that is the loadtodayreal · survived 1760d
A response-size cap, implemented in the stream handler. Correct on every input the tests use. Survived 1760 days.
JavaScriptNode streamsMinedSenior— - 13
Counted twice, oncereal · survived 3462d
A response wrapper that reports how many bytes it wrote. Both branches look symmetrical. Only one of them should be. 3462 days.
Gonet/httpMinedSenior— - 14
Both, it says herereal · survived 255d
Support a static key set and a remote JWKS endpoint, and both together. Four lines, correct on the first request. Survived 255 days.
TypeScriptJWTMinedSenior— - 15
Partial, as declaredreal · survived 189d
A setter typed `Partial<RetryOptions>`, validated key by key against the defaults it is about to discard. Survived 189 days.
TypeScriptHTTP clientMinedSenior— - 16
Absolute, according to whomreal · survived 3187d
Fifteen lines, one regex, one optional group. It shipped in a library you depend on and stayed wrong for 3187 days.
JavaScriptHTTP clientMinedPrincipal—