magpie-reviewer-routing

<!-- SPDX-License-Identifier: Apache-2.0 https://www.apache.org/licenses/LICENSE-2.0 --> <!-- Placeholder convention (see ../../AGENTS.md#placeholder-convention-used-in-skill-files): <upstream> → GitHub slug of the upstream codebase <project-config> → the adopting project's config directory <default-branch> → upstream's default branch (master vs main) <N> → an issue or PR number Substitute these with concrete values from the adopting project's <project-config>/ before running any command below. --> # reviewer-routing This skill removes the "who should look at this?" pause that stalls a fresh PR or issue before any review begins. Given an open issue or PR it scores the project's configured reviewer roster and proposes one primary reviewer (and optionally a backup), grounding each suggestion in three signals: 1. **Roster eligibility for the touched area** — each roster entry declares which components, paths, or areas it covers; the skill matches the issue/PR's labels, changed paths, and title against those declarations. 2. **Git-history familiarity with the changed paths** — for PRs, the skill scans the upstream git log on the changed files to surface who has authored or reviewed changes to those paths recently. 3. **Current open-review load** — the skill counts each roster member's open review-requested PRs on `<upstream>` so routing spreads work instead of piling it on the most recently active ...