review-routing

Route code review and security analysis tasks to appropriate engines.

Updated Jul 5, 2026
One-click install
npx skills add https://github.com/danwan/coding-agent --skill review-routing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-routing
Source: https://github.com/danwan/coding-agent/tree/main/sources/skills/review-routing
Command: npx skills add https://github.com/danwan/coding-agent --skill review-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves ambiguity in choosing the right review tool, preventing wasted effort and ensuring the correct engine is used for specific development phases like diff reviews, security scans, or whole-repo analysis.

Core Features & Use Cases

  • Engine Routing: Clearly defines when to use built-in native tools versus external SaaS engines like CodeRabbit or Greptile.
  • Context-Aware Dispatch: Provides a decision matrix for different project needs, such as quick diff reviews, security audits, or complex refactoring.
  • Use Case: When you are unsure whether to use a built-in security scan or an external tool for a large PR, this skill provides the definitive logic to choose the most cost-effective and accurate path.

Quick Start

Ask the agent to review your current changes using the appropriate routing logic based on your project requirements.

Frequently Asked Questions about review-routing

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

FAQPage Schema
How do I choose the right code review tool for different development phases?

To choose the right code review tool, use a decision matrix that evaluates project context like quick diff reviews, security audits, or complex refactoring, routing the task to the most cost-effective and accurate engine.

When should I use built-in native review tools versus external engines like CodeRabbit or Greptile?

Use built-in native review tools for standard iterative development and quick diff reviews, whereas external engines like CodeRabbit or Greptile are routed for whole-repo security auditing and complex analysis tasks.

How do I standardize security scans and code review workflows across multiple engines?

You standardize security scans and code review workflows by applying context-aware dispatch logic that resolves namespace collisions and optimizes resource usage across built-in tools, CodeRabbit CLI, and Greptile MCP tools.

What is the best way to automate pre-PR verification and whole-repo security auditing?

The best way to automate pre-PR verification and whole-repo security auditing is to implement engine routing logic that dispatches tasks based on a decision matrix tailored to your specific project requirements.

Does code review routing work without integrating external SaaS engines?

Code review routing requires integration with built-in native skills, CodeRabbit CLI, and Greptile MCP tools to fully resolve namespace collisions, optimize resource usage, and apply the definitive selection logic.

Why does selecting a review engine manually cause wasted effort during code reviews?

Selecting a review engine manually causes wasted effort because of ambiguity in choosing the right tool, which prevents the correct engine from being used for specific development phases like diff reviews or security scans.