human-review-routing

Patch routing assigns risky code changes to appropriate reviewers by analyzing content and risk signals. It supports security, backend, infra, frontend, data, and devops reviewer types, including multi-reviewer routing when patches touch multiple concerns.

Patch Trust Score evaluation influences routing decisions by acting as a risk signal that helps determine the appropriate reviewer type and escalation level. High-risk scores trigger escalation rules to ensure sensitive patches receive specialized scrutiny.

When no keywords match during patch routing, the system applies an escalation and fallback mechanism. It routes the patch to a general-reviewer to ensure changes are still examined without stalling the development pipeline.

Yes, you can assign multiple reviewers when a patch touches multiple concerns like backend and security. The system supports multi-reviewer routing, distributing review responsibilities across the relevant domain experts.

To get a patch routing decision, you need to provide the files changed and a short change description. The agent analyzes these inputs alongside risk signals to output clear routing decisions for the appropriate reviewers.