Skip to main content
Review Insights shows review activity, recurring findings, and evidence-backed trends across your repositories. Open it from Review → Insights in the navigation.

​
Insights tabs

Review Insights has two tabs: Review Patterns opens by default.

​
Review Patterns

Review Patterns is the coaching view. It shows, per developer and per domain, how often reviewed work merged without findings — and links each rate to the findings behind it.

​
What counts

Review Patterns counts completed Advanced Reviews on merge requests with a recorded outcome. Fast Reviews, incomplete reviews, pipeline findings, and merge requests from bot authors are not counted. Older merge requests without a recorded outcome stay excluded — Review Patterns never guesses an outcome from timestamps.

​
Reading the rates

The view covers four domains: Security, Performance, Correctness, and Patterns. Each domain shows the finding-free merge-request rate together with the exact counts behind it. A domain rate is:
One merge request counts once in a selected period, even when it was reviewed more than once — findings from all of its counted reviews feed the domain rates, and several findings in one domain still count the merge request once. Resolved and unresolved findings count equally. A developer with fewer than three counted merge requests stays visible with Not enough data and the reviewed count. Their merge requests still contribute to the pooled team rate.

​
Main coaching priority

The page headlines the domain with the highest team-wide affected merge-request rate. An exact tie breaks on the Critical and High finding counts, and every domain still tied appears. Severity never weights a rate.

​
Explore evidence

Select a developer-domain cell to see the developer and pooled team across the selected weekly or monthly buckets. The expanded view lists the associated findings with severity, resolution state, merge-request identity, and a review link. A resolved finding remains historical coaching evidence.

​
Periods and states

The weekly and monthly controls apply to Review Patterns. The view keeps your selections while data loads. The view handles thin periods explicitly:
  • No counted reviews in the period: the page explains that the period has no data.
  • One or two counted merge requests: the view shows counts without a percentage.
  • No counted merge requests in a trend bucket: the chart shows a gap labelled No data.
  • If loading fails, the affected panel offers Retry and keeps your period selection.

Review Setup

Connect repositories and choose where CloudThinker reviews code

Learnings

Encode team standards to reduce recurring findings

Review Overview

Learn how CloudThinker reviews merge requests and reports findings