paw-review-impact

To analyze the system-wide impact of PR changes, you can generate an ImpactAnalysis.md that maps integration dependencies, detects breaking changes, and highlights performance and security implications across affected modules.

Cross-repo impact analysis works by examining ReviewContext.md, CodeResearch.md, and DerivedSpec.md to build a dependency graph that identifies public API or data model changes requiring migrations. It then surfaces these integration points in an ImpactAnalysis.md.

The best way to assess deployment risks for a PR is to evaluate deployment considerations, rollback plans, and migration needs by mapping how the changes ripple through the system. This risk assessment is then documented to guide reviewers.

Yes, this impact analysis skill applies to cross-repo scenarios by mapping dependencies across modules and services. It evaluates how PR changes affect integration points, data models, and deployment considerations throughout the wider system architecture.

You need to provide ReviewContext.md, CodeResearch.md, and DerivedSpec.md as baseline artifacts for a comprehensive PR impact analysis. These inputs allow the skill to surface dependencies, design implications, and migration needs accurately.

You need a dedicated risk assessment for breaking changes when a PR touches core APIs, data models, or interfaces. This ensures reviewers understand system-wide impacts, performance implications, security considerations, and required migration steps.