pr-review-router

Route PR review requests to code-review or pr-review-toolkit based on intent.

3|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/t6adev/claude-code-tools --skill pr-review-router
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review-router
Source: https://github.com/t6adev/claude-code-tools/tree/main/tools/skills/code/pr-review-router
Command: npx skills add https://github.com/t6adev/claude-code-tools --skill pr-review-router

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route a PR review request to the correct tool — code-review for quick parallel scanning or pr-review-toolkit for a deep-dive into a specific quality dimension (e.g., type design, error handling, test quality, or documentation). Use when a user asks for a code review, PR review, or mentions a particular concern before creating a PR.

Core Features & Use Cases

  • Intent-driven routing from user input or conversation context to the appropriate tooling.
  • Maps signals to either the code-review plugin (parallel, broad scan) or the pr-review-toolkit (focused analysis by specialized agents).
  • Returns a concise execution plan including the chosen tool, justification, and a non-executing invocation guide; this requires the relevant plugins to be installed.

Quick Start

Ask the user for their review intent and route the request to the appropriate tool without executing it.

Frequently Asked Questions about pr-review-router

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

FAQPage Schema
How do I automatically route PR review requests to the right tool?

Automatically route PR review requests by analyzing intent signals from user input and mapping them to either a broad parallel scan or a deep-dive quality analysis tool. The router evaluates the context and returns the chosen tool name with an invocation guide.

What is intent-driven code review routing?

Intent-driven code review routing is a mechanism that analyzes user requests to determine the review scope. It maps conversational signals to the appropriate tooling, returning a concise execution plan with a justification rather than executing the review immediately.

When should I use a broad code scan vs a deep-dive PR review?

Use a broad code scan for quick parallel checks across a repository, and use a deep-dive PR review when you mention a specific quality concern like type design, error handling, test quality, or documentation before creating a PR.

Do I need plugins installed to use the PR review router?

Yes, you need the code-review plugin and the pr-review-toolkit installed. The router returns an invocation guide and assumes these underlying tools are present in your environment to execute the actual code analysis.

Does the PR review router execute the code analysis directly?

No, the PR review router does not execute code analysis directly. It provides a non-executing invocation guide and justification for the selected tool, requiring you to run the actual review tool separately.