cross-repo-pr-review

Reviews multiple linked pull requests as one cross-repo feature with contract and rollout analysis.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/toderian/project_template --skill cross-repo-pr-review-toderian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cross-repo-pr-review
Source: https://github.com/toderian/project_template/tree/main/plugins/agents-tasks/skills/cross-repo-pr-review
Command: npx skills add https://github.com/toderian/project_template --skill cross-repo-pr-review-toderian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Single-PR review misses integration failures that only appear when changes span multiple repositories, such as broken contracts between a shared library and its consumers, unsafe rollout ordering, or old/new version incompatibility across independently deployed components. ## Core Features & Use Cases - Contract Reconstruction: Builds or locates a cross-repo feature contract covering APIs, schemas, versions, publish order, and compatibility combinations, then reviews every PR against it. - Isolated Per-PR Inspection Plus Integration Synthesis: Inventories each PR separately (surfaces, dependencies, tests, CI) before synthesizing cross-repo blockers, per-PR blockers, follow-ups, and discarded noise. - Structured Verdict Report: Produces a severity-classified report with overall verdict, merge/rollout order, cross-repo and per-PR findings, test gaps, open questions, and checks run. - Use Case: A feature touches a core types package, a backend service, and a web UI across three repos. The skill reviews all three PRs together, catches that the UI assumes a backend field that only exists after a specific deploy order, and flags it as a cross-repo blocker with a suggested fix. ## Quick Start Ask the assistant to review these linked pull requests together as one cross-repo feature and paste the PR URLs for each affected repository.

Frequently Asked Questions about cross-repo-pr-review

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

FAQPage Schema
How do I review multiple pull requests across different repositories together?

Provide the PR URLs, repo names, or branch names for every repository in the feature, plus any release constraints like version pins or deploy order. The review reconstructs the shared contract, inspects each PR in isolation, then synthesizes cross-repo findings with a merge order and verdict.

What does a cross-repo PR review check that a normal PR review misses?

It checks contract compatibility between producers and consumers, old/new version combinations, package publish order, migration safety under partial rollout, and rollback behavior. These integration failures are invisible when each PR is reviewed alone.

Can I use this to self-review my own PRs before asking teammates?

Yes. The process supports author-side self-review by running the same phases and biasing output toward surgical file-and-line fixes the author can apply before peers spend time reviewing.

What happens if one of the referenced pull requests is unavailable?

The review continues with the remaining PRs and marks the missing PR as a blocker or limitation depending on its risk. The final report states exactly what could not be verified and how that affects confidence.

When is a full cross-repo review not necessary?

Depth scales to risk: a small config-only follower PR may only need a quick compatibility pass. Full deep review is reserved for versioned APIs, migrations, auth changes, generated artifacts, and shared library changes.