PR Quality Estimator
Score any pull request 0-100 from its diff size, tests, description and linked issue - with a plain-English rationale and concrete tips to raise it.
The pull request
Weights are illustrative, editable defaults - a fast sanity check, not a benchmark.
Estimate
0-100Estimated 89/100 - strong. This is because the diff is a reviewable size, tests ship alongside the change, nothing links the change back to a tracked issue.
Tips
- Link an issue or ticket so the change is traceable.
What makes a high-quality pull request?
Pull request quality is less about clever code and more about reviewability. A change that ships tests, carries a clear description, links back to a tracked issue, and stays small is one a reviewer can actually reason about. This estimator turns those signals into a single 0-100 score so you can spot risky PRs before they land.
Diff size is the strongest lever. Large, sprawling changes get shallow reviews and hide regressions, while focused PRs get merged faster with better feedback. If your score is low, the fastest win is usually to split the change and add the tests that prove it works. For deeper patterns across your repo, see our PR quality analytics and cycle time analytics.
The heuristic here mirrors well-known review guidance, but it is a starting point - calibrate it against how your team actually works. To go further, read our guide on code review best practices or explore the full set of free engineering tools.
Frequently asked questions
Measure what your team actually ships
FeatureFactory tracks PR quality, cycle time and AI-generated code across your whole repo - the feature factory that measures what it ships.
Get early access