Awesome Reviewers

Verification · Code review

Reviewer routing

Chooses which specialist reviewers, human or automated, apply to a change based on its files, topics and history.

Sub-techniques

  • Path ownership V1041.001

    Route by file path ownership rules.

  • Semantic matching V1041.002

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

  • Reviewer merging V1041.003

    Combine overlapping reviewers so one concern is not reviewed twice.

How to build it

  1. Start with CODEOWNERS for humans.
  2. Describe each automated reviewer in one paragraph and match changes to it.
  3. Log which reviewer produced accepted findings and prune the rest.

Signals in a repository

  • CODEOWNERS, review assignment bots, or reviewer config files.