The quality of a PR is measured by the comments or by the lack of them?

This question caught me off guard and completely changed how I view code reviews.

Have you ever heard of the PR Maturity Ratio? It’s a metric that measures how "ready" a PR is when it gets to the review stage.

The PR Maturity Ratio is super simple:

- Take the total number of changes in the PR.
- Subtract the changes made after it was opened.
- Divide by the total number of changes.

For example: a PR with 100 modified lines and 20 adjusted after it was opened would have a ratio of 80%.

And what does that mean?

- PRs with a high ratio (above 90%) get approved faster.
- Large PRs with no context have low ratios and block the workflow.
- Reviewers prefer mature PRs because they require less rework and are clearer.

If I had understood this earlier, I could’ve avoided so many problems: massive PRs, unnecessary rework, and long reviews that delayed deliveries.

At the end of the day, the quality of a PR isn’t about the number of comments—it’s about how ready it is when it gets to review.

This is the key to unlocking productivity and improving review workflows.

Does your team use any similar metrics?