Find the handoffs that leave reviews waiting.

Start with your review queue, not another notification feed. Review Router's free tools show where pull requests lack an owner, wait too long, or depend on the same reviewer.

Public repository: no account needed

Open the free PR review-health check and enter a public GitHub repository. The report includes stale PRs, missing reviewers, median first-review time and reviewer concentration. Copy its README badge if you want a live link to the report.

Private repository or CODEOWNERS audit: use GitHub Actions

The Audit Action also checks changed files for CODEOWNERS matches and reviewers with many outstanding requests. Add this workflow as .github/workflows/review-health.yml, then run it from the repository's Actions tab.

name: Review health
on:
  workflow_dispatch:
  schedule:
    - cron: "17 9 * * 1"
permissions:
  contents: read
  pull-requests: read
jobs:
  audit:
    runs-on: ubuntu-latest
    steps:
      - uses: tenpace-app/review-router-audit@v1

By default, the Action uses the repository-scoped GitHub token, writes a job summary and JSON report, and sends no repository data to Tenpace. PR comments and setup-link creation are opt-in. Do not publish private reports or use the public badge for a private repository.

Read the evidence, not just the score

Stale PRs: investigate why work has stopped. The default threshold is seven days without an update, not seven days without a review.
Missing owners: no requested reviewer, requested team or assignee is present. That does not prove nobody is reviewing informally.
First-review time: the median time to the first submitted review in the sampled closed PRs. It is not merge time.
CODEOWNERS gaps: changed files without a matching ownership rule. A match alone does not prove that an owner is available.
Reviewer concentration: use it to discuss workload, never as an individual productivity ranking.

Turn one finding into one better handoff

Choose one repository with a recurring ownership or notification problem.
Choose a Slack channel that the responsible team already uses.
Ask your assistant to propose a route, or follow the manual setup guide.
Check the verification message, then confirm that a real matching PR reaches that channel.
Run the audit again after enough comparable PRs. Compare the same thresholds and sample size before making claims about improvement.

Already getting the notifications you need from GitHub's Slack integration? Keep using it. Review Router is useful when you need configurable channel routing, reviewer mentions, and an updating message that keeps ownership visible. It complements your code review process; it does not replace code review.

Action inputs, outputs and source · GitHub's Slack notification documentation · Review Router notification rules