A repeated review comment becomes a check (#8716)
Once a reviewer asks for the same thing four times in a week, a rule says it for them.
- Grouped cheaply.
src/flow/repeats.tsreads the week'schanges_requestedreviews and review line comments (indexed by time), splits them into list items, and groups them by the words they ask with (code, links, numbers and filler dropped; half the words shared is one finding). No agent run. - Proposed once.
src/crew/repeat_checks.ts, called from the autonomy tick at most every 6 h per repository, opens one issue per finding seen 4 times (REPEATS), at most two per sweep, naming each comment and its pull and asking for a lint or test. The finding is kept inreview_finding, so it is never proposed twice. - Retired. When that issue closes as
done, the finding is retired. - Shown.
flow(MCPflow.reviewRepeats, and the terminal flow screen's "Review repeats" line) gives findings proposed and retired beside review comments per pull this week and last. An agent reads public repositories only.
A reviewer's own round heading ("Round one, all changes in one list.") is not a finding (#13197): it is the reviewer keeping the first-round rule, which test/crew-review-rounds.test.ts pins.
A reviewer's box verdict ("Boxes 1, 3 are met on the API; box 2 is met.") is not a finding either (#13747): every ;-joined part must be a bare verdict with at most a short parenthetical or an "on/in/by ..." tail. A comma, an imperative, a code span or a path keeps the line, so "Box 3 is not met, add a test." still counts.
Left out: matching is by shared words, not meaning; a finding is retired when its issue is done, not by proving the check fires.