The code review practices report tracks several metrics related to code review health and adherence to code review standards across teams.

The first section of the report contains scorecard metrics for code review rate (CRR), which is the total percentage of active dev time spent on pull requests that ever receive any review, and thorough review rate (TRR), which is the amount of time spent on branches that receive any substantive comment other than a rubber-stamp approval.

The thorough review rate is important because sometimes people may follow code review guidelines by the letter, but not actually review the code very carefully and provide rubber-stamp reviews (just approving without comment), which defeats the purpose of code review guidelines.

Next, the report shows PR open to first review time (PRRT) to help spot bottlenecks in the review process, which can drive up cycle times and negatively impact other downstream metrics.

The report then shows the number of substantive reviews per pull request (SRPR) both by team and with an absolute count. Note here that the numbers can be over 100% if there are multiple reviews.

Finally, the report shows individual high-comment PRs (HCPR), which can indicate pull requests that have issues and require a lot of back-and-forth before merging.