> For the complete documentation index, see [llms.txt](https://docs.hivel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hivel.ai/using-hivel/cockpit/metrics-and-definitions/quality/unreviewed-prs.md).

# Unreviewed PRs

<div data-with-frame="true"><figure><img src="https://3057781534-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5KAIOUWph0JLSgQqbzyT%2Fuploads%2FzoCskm6csRVbD8RKh0ae%2FScreenshot%202025-11-28%20at%2012.28.49%E2%80%AFPM.png?alt=media&amp;token=71d7b643-edc1-401e-9f4f-6bf7233c5068" alt=""><figcaption></figcaption></figure></div>

#### All merged PRs that do not have a review state are PRs merged without review.&#x20;

* Reviewing every PR saves a lot of post-production issues and can keep higher quality across.
* Merging PRs without review is a symptom of production issues or poor-quality code that could lead to higher maintenance issues in the future. Also, junior engineers miss out on learning opportunities.

#### Industry Benchmarking

<div data-with-frame="true"><figure><img src="https://3057781534-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5KAIOUWph0JLSgQqbzyT%2Fuploads%2FHcUOpTST4yG3BaJlk5ON%2Fimage.png?alt=media&amp;token=a7463288-0cc6-4847-972f-5d975c75fc6e" alt=""><figcaption></figcaption></figure></div>

#### Related article

{% content-ref url="/pages/rCCVl6PcU9i0FwS9a0ur" %}
[Best Practices for Ensuring Strong Pull Request Review Coverage](/improve-performance/how-to-improve-quality/best-practices-for-ensuring-strong-pull-request-review-coverage.md)
{% endcontent-ref %}

{% content-ref url="/pages/d0Bwgwr0hUbUY391RVlY" %}
[Best Practices for Team Ownership in Code Review](/improve-performance/how-to-improve-quality/best-practices-for-team-ownership-in-code-review.md)
{% endcontent-ref %}