Reviewer routing
Chooses which specialist reviewers, human or automated, apply to a change based on its files, topics and history.
Sub-techniques
3
| ID | Name | Description |
|---|---|---|
V1041.001 | Path ownership | Route by file path ownership rules. |
V1041.002 | Semantic matching | Match the change to reviewer descriptions by embedding similarity and reranking. |
V1041.003 | Reviewer merging | Combine overlapping reviewers so one concern is not reviewed twice. |
Craft it
- Start with CODEOWNERS for humans.
- Describe each automated reviewer in one paragraph and match changes to it.
- Log which reviewer produced accepted findings and prune the rest.
Reverse engineer it
Signs that a codebase already runs this technique, and where to read how it is configured.
- CODEOWNERS, review assignment bots, or reviewer config files.
Open-source packages
3
- Sentence Transformers huggingface/sentence-transformers
- rerankers AnswerDotAI/rerankers
- SetFit huggingface/setfit