magpie-reviewer-routing

Suggest suitable pull request reviewers based on expertise, familiarity, and workload.

79|76|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/apache/magpie --skill magpie-reviewer-routing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: magpie-reviewer-routing
Source: https://github.com/apache/magpie/tree/main/skills/reviewer-routing
Command: npx skills add https://github.com/apache/magpie --skill magpie-reviewer-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, python, and includes scripts (resource) components.

What problem does it solve?

This Skill identifies suitable reviewers for pull requests by considering the expertise of the reviewers, their familiarity with the changed paths in the PR, and their current workload.

Core Features & Use Cases

  • Area Eligibility: Matches reviewers based on their declared expertise areas.

  • Git History Familiarity: Considers the history of code contributions by potential reviewers.

  • Review Load Analysis: Proposes reviewers with a balanced workload to prevent overburdening any individual.

  • Use Case: When a maintainer wants to assign a reviewer for a pull request, this Skill suggests an appropriate candidate, based on their expertise in the code being modified and their past review activity.

Quick Start

To propose a reviewer for PR #123 in the repository 'org/repo', run: reviewer-routing pr:123 --repo org/repo

Frequently Asked Questions about magpie-reviewer-routing

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

FAQPage Schema
How do I assign pull request reviewers based on code expertise and workload?

To assign pull request reviewers based on code expertise and workload, you can use an automated routing script that matches area eligibility, git history familiarity, and current review load to prevent overburdening specific developers.

Can I automatically suggest reviewers for a GitHub pull request?

Yes, you can automatically suggest reviewers for a GitHub pull request by running a Python script integrated with the gh CLI. It analyzes contribution history and developer workload to propose suitable candidates.

Do I need the gh CLI to route pull request reviewers in CI/CD workflows?

Yes, you need the gh CLI installed to route pull request reviewers in CI/CD workflows. The Python backend uses gh for GitHub integration to fetch pull request details, contribution history, and current review activity.

How does review load analysis work when assigning pull requests?

Review load analysis works by tracking current open review assignments for each developer. It proposes reviewers with a balanced workload, preventing any individual from being overburdened by too many concurrent pull request reviews.

What is the best way to find reviewers familiar with specific code paths?

The best way to find reviewers familiar with specific code paths is to analyze git history familiarity. This approach matches potential reviewers based on their past contributions to the exact files modified in the pull request.