Review this diff as someone who has never seen your codebase
Ranked findings with severity, location, and a concrete failure scenario for each; what was reviewed and what was not; nothing rewritten for you.
Paste a diff and the one thing it must not break. An Agent that has never seen your conversation, your repo, or your reasoning reads it cold and tells you what it would flag. It does not fix anything; it gives you findings you can turn into tests.
Good for
A developer who wrote or generated a change and wants it attacked by a reader with none of their context before it goes to review.
Not for
Style feedback, a rewrite, or a review of a whole feature spread over many files.
What you give
- The diff (unified format is fine)
- What this change must not break
- Language
- Anything you are already worried about (optional)
What you get back
- 1. Verdict in one line
- 2. Findings, worst first
- 3. What was reviewed and what was not
- 4. Assumptions made
- 5. If nothing blocking: the cases checked that pass
Example
See an example
## Verdict in one line One should-fix: the retry loop can double-charge when the first attempt times out after the write commits. ## Findings, worst first 1. **should-fix — `charge.ts`, hunk @@ -41,7 +41,12 @@.** Scenario: (1) the POST commits the charge row, (2) the client times out before the response, (3) the retry reuses the idempotency key but reads the key cache before the commit is visible, (4) a second charge row is written. Reproduce with an integration test that delays the commit past the client timeout. 2. **note — `charge.ts`, same hunk.** The retry counter is reset on every call, so the cap of three retries is never reached across a process restart. ## What was reviewed and what was not Reviewed both hunks against the invariant "never charge twice". Not reviewed: the idempotency cache implementation, which is outside the diff and decides whether finding 1 is reachable. ## Assumptions made Idempotency keys are per request, not per customer. The cache is not transactional with the charge table. ## If nothing blocking: the cases checked that pass Concurrent retries with distinct keys; a retry after a 4xx; a retry after the response was received.
Details
- Response
- One answer
- Time
- About 2 min
- To run
- 500 Credits
Pumasi's Agent handles your inputs.