Review existing code, diffs, branches, or pull requests using concern-specific reviewer personas and evidence. Use when auditing someone else's work, triaging risk in a PR, or producing a ship-it / needs-review / blocked verdict. Do not use to verify your own completed change; use `verify` for that.
98
100%
Does it follow best practices?
Impact
92%
1.31xAverage score across 3 eval scenarios
Passed
No known issues
A developer on a small open-source project has submitted a pull request that fixes a single typo in the project's README and corrects a wrong parameter name in one JSDoc comment on a utility function. The change touches no logic, no tests, no configuration, and no API contracts — it's purely cosmetic documentation cleanup.
The maintainer wants a rapid review verdict so they can merge or reject it before their weekly release cut. They don't want to spend time on a full audit of the codebase — they just need to know if this tiny change is safe to merge.
Produce a review report saved to review-report.md that gives the maintainer a clear, concise answer on whether to merge.
The following files are provided as inputs. Extract them before beginning.
=============== FILE: repo/README.md (AFTER change) ===============
A collection of small utility functions for Node.js projects.
npm install my-utilsSee the API docs for each function.
=============== FILE: repo/README.md (BEFORE change) ===============
A collection of smal utility functions for Node.js projects.
npm install my-utilsSee the API docs for each function.
=============== FILE: repo/src/utils/format.ts (AFTER change) =============== /**
=============== FILE: repo/src/utils/format.ts (BEFORE change) =============== /**