paw-review-correlation

Synthesize cross-repo PR findings into a dependency graph and CrossRepoAnalysis.md.

39|6|Updated Oct 8, 2025
One-click install
npx skills add https://github.com/lossyrob/phased-agent-workflow --skill paw-review-correlation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paw-review-correlation
Source: https://github.com/lossyrob/phased-agent-workflow/tree/main/skills/paw-review-correlation
Command: npx skills add https://github.com/lossyrob/phased-agent-workflow --skill paw-review-correlation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill consolidates findings from multiple PR reviews across repositories to reveal hidden dependencies, interface contract mismatches, and coordination gaps that are not evident when analyzing PRs individually.

Core Features & Use Cases

  • Cross-Repo Dependency Graph: maps which repositories export interfaces and which consume them.
  • Interface Contract Detection: identifies mismatches and potential breaking changes.
  • Deployment Coordination: suggests sequencing and rollout considerations across repos.
  • Comprehensive Artifacts: generates a CrossRepoAnalysis.md summarizing findings for audit and rollout planning.

Quick Start

Run the cross-repo correlation workflow on a multi-PR review set and review the CrossRepoAnalysis.md artifact.

Frequently Asked Questions about paw-review-correlation

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

FAQPage Schema
How do I identify cross-repo dependencies and interface mismatches across multiple PRs?

Cross-repo dependency analysis synthesizes per-PR artifacts like ReviewContext.md and DerivedSpec.md to map interface contracts and identify mismatches across repositories. It compiles findings into a CrossRepoAnalysis.md artifact with actionable coordination recommendations.

What is a cross-repo PR review correlation workflow?

A cross-repo PR review correlation workflow consolidates individual PR reviews to reveal hidden dependencies, interface contract mismatches, and coordination gaps that are not evident when analyzing PRs individually. It builds a coherent dependency graph from per-PR artifacts.

Do I need specific artifacts to perform cross-repo dependency graph analysis?

Yes, cross-repo dependency graph analysis requires per-PR artifacts such as ReviewContext.md, ImpactAnalysis.md, and DerivedSpec.md to build a coherent dependency graph and generate comprehensive cross-repo findings.

How do I coordinate deployment sequencing across repositories with interface contracts?

Deployment coordination across repositories analyzes interface contracts and dependency graphs to suggest rollout sequencing and considerations. It outputs a CrossRepoAnalysis.md summarizing deployment sequencing findings for audit and rollout planning.

What's the best way to detect breaking interface contract changes in a multi-repo codebase?

Interface contract detection maps which repositories export interfaces and which consume them to identify mismatches and potential breaking changes. It synthesizes cross-repo PR findings to reveal coordination gaps across repositories.

When should I not use cross-repo correlation for PR review?

Cross-repo correlation is not suited for single-repository PR reviews or workflows lacking per-PR artifacts like ImpactAnalysis.md and DerivedSpec.md. It requires multi-repo review workflows to build a coherent dependency graph and compile cross-repo analysis.