human-review-routing

Route patches to appropriate human reviewers using keyword and risk analysis.

20|3|Updated Apr 30, 2026

Search Tags:#security #backend #infrastructure #review #patch #route #trust-score

Ready to run

npx skills add https://github.com/DVNghiem/FlowDeck --skill human-review-routing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: human-review-routing
Source: https://github.com/DVNghiem/FlowDeck/tree/main/src/skills/human-review-routing
Command: npx skills add https://github.com/DVNghiem/FlowDeck --skill human-review-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically route risky patches to the most appropriate human reviewer based on patch content and risk signals.

Core Features & Use Cases

Keyword-based routing to security, backend, infra, domain-owner, frontend, data, and devops reviewers
Patch Trust Score integration to influence routing decisions
Multi-reviewer routing when patches touch multiple concerns
Escalation and fallback to a general-reviewer when no keywords match

Quick Start

Provide the files changed and a short change description to the agent to obtain the routing decision.

Frequently Asked Questions about human-review-routing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automatically route code patches to the right human reviewer?▼

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.

How does Patch Trust Score evaluation influence routing decisions?▼

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.

What happens when no keywords match during patch routing?▼

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.

Can I assign multiple reviewers when a patch touches backend and security concerns?▼

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.

What information do I need to provide to get a patch routing decision?▼

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.