Awesome Reviewers

Verification · Code review · Reviewer routing

Semantic matching

Match the change to reviewer descriptions by embedding similarity and reranking.

How to build it

  1. Write a one-paragraph description for each automated reviewer.
  2. Embed each description and a summary of each changed file.
  3. Rerank the top matches and assign reviewers above a set score.

Signals in a repository

  • A reviewer description file that the routing script reads.
  • A routing script or bot config that scores changes against reviewer descriptions.
  • Routing decisions logged on pull requests with their scores.

In practice

No scanned repository runs a tool for this check. The steps above are the only guidance.