Review Suite reviews a pull request with a panel, not a single pass: one reviewer each for correctness, security, the compatibility of public interfaces and test coverage, an adjudicator that merges their findings and ranks them, and a verifier that has to reproduce each finding, with a failing test or a run that shows the problem, before it reaches you. A finding nobody could reproduce is listed at the end as a doubt, not as a finding.
Usage
Check out the pull request's branch.
Start Review with the base branch (default main).
Read the summary first; the verified findings follow, each with its reproduction: unauthorized access and data loss first, then broken behaviour, then the rest.
What it produces
review/summary.md: the change in a few sentences, the riskiest files first, and open questions
review/findings.md: each verified finding with the file and line, the reviewer that raised it, and the test or command that reproduces it
review/tests/: the failing tests the verifier wrote, ready to keep once the problem is fixed
review/comments.md: line comments you can paste into your Git host
Configuration
base (default main): the branch to compare against.
reviewers (default: all four): who sits on the panel; focus adds a question for all of them, such as performance.
.review-ignore: paths to skip, such as generated files.
Notes
It runs single tests to verify findings, not the whole suite.
The reviewers' prompts are one file in the package, a section each: edit one, add a fifth, or fork the suite for your team's rules.
