main/e5520b/repo-insights
e5520bfeat: see how the team ships main

See where pull requests wait.

Repo Insights shows PR cycle time, time to first review, review load and delivery trends across repositories. It is designed to improve how a team works together, not to rank or judge individual developers.

Repo Insights · platform team · last 8 weeksteam view
Median PR cycle time24 h-48% vs. week 1
Time to first review3.1 hwas 9.2 h
PRs merged / week63+11
Avg. PR size212lines changed
Median cycle time (hours)
46W1
41W2
44W3
38W4
33W5
30W6
27W7
24W8
Review load spread
0-2 / wk2
3-5 / wk7
6-8 / wk5
9+ / wk1

Reviewers per load band. Flags when review work piles up on a few people, without naming or ranking anyone.

CHANGELOG Repo Insights

Measures that help a team flow

Every chart is at team or repository level. Insights helps you fix process bottlenecks: slow reviews, oversized PRs and uneven review load.

Cycle time, broken downCoding time, waiting for first review, in review, and waiting to merge, so you know which stage to fix.
Time to first reviewHow long PRs sit before anyone, human or Megicoder, looks at them.
Review load spreadWhether review work is shared or piling up on a few people, shown as a distribution.
PR size trendsLarge PRs get slower, shallower reviews. Track size and its effect on cycle time.
Delivery trendsPRs merged per week, rework rate and how often merged code gets reverted.

Team dashboards

One view per team, built from the repositories that team owns.

Wait-time alerts

Slack nudges when a PR has waited longer than your agreed review time.

PR size guidance

Suggest splitting a PR when it crosses the size where your reviews start slowing down.

No individual ranking

There are no per-developer leaderboards or scores. This is a product decision, not a setting.

Across teams on Enterprise

Compare flow across teams and business units with shared definitions.

Before and after

See how cycle time changed after adopting AI review or a new review policy.

Built for team flowRepo Insights is for improving how work moves through a team. It is not designed for ranking or judging individual developers, and it does not offer per-person scores.
git log --questions repo-insights

Common questions

No. Repo Insights reports at team and repository level only. Review load is shown as a distribution, not a list of names.

From pull request events on your git platform: opened, reviewed, approved, merged and reverted. No IDE tracking or keystroke data.

Team includes Repo Insights per team. Enterprise adds views across teams.

git merge feat/first-review into main

Review your
first repo free.

One repository, AI review on every pull request, no time limit. Connect it in about five minutes and the next PR gets a first pass in under a minute.

Review 1 repo free