After enabling Code Review with default settings on a service repository, a lead notices that no findings mention missing unit tests or inconsistent formatting, even on PRs that clearly have both. What explains this?
Choose an answer to check it. Afterward, select any option to review its explanation.
The trigger setting decides when a review runs and how much it costs, not what kinds of issues the review looks for.
The check run repeats the same findings as the inline comments in a severity table; it is not a separate home for style or test findings. If the review never produced them, they appear nowhere.
Out of the box, Code Review is calibrated for correctness: bugs that would break production. Formatting preferences and test coverage are outside that default, and a team that wants them flagged has to add guidance files.
Replying to an inline comment does not prompt Claude to respond or re-review, so replies cannot unlock new categories of findings.
id q48e8b5cc63