paw-review-impact

Analyzes PR changes and produces an ImpactAnalysis.md report.

39|6|Updated Oct 8, 2025

Search Tags:#integration #risk-assessment #PR #code-review #impact-analysis #cross-repo

Ready to run

npx skills add https://github.com/lossyrob/phased-agent-workflow --skill paw-review-impact

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: paw-review-impact
Source: https://github.com/lossyrob/phased-agent-workflow/tree/main/skills/paw-review-impact
Command: npx skills add https://github.com/lossyrob/phased-agent-workflow --skill paw-review-impact

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams understand how PR changes ripple through a system by mapping dependencies, detecting breaking changes, and highlighting performance and security implications.

Core Features & Use Cases

Integration impact mapping: Builds a dependency graph showing which modules and services are affected by the PR.
Breaking changes detection: Identifies public API, data model, or interface changes that could require migrations or compatibility work.
Risk assessment & deployment guidance: Evaluates deployment considerations, rollback plans, and migration needs.
Use Case: For a PR touching a core API, generate a comprehensive ImpactAnalysis.md to guide reviewers and engineers on impacts and rollout steps.

Quick Start

Use the paw-review-impact skill to generate an ImpactAnalysis.md for the current PR, referencing ReviewContext.md, CodeResearch.md, and DerivedSpec.md as baselines.

Frequently Asked Questions about paw-review-impact

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

FAQPage Schema

How do I analyze the system-wide impact of PR changes on my codebase?▼

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.

How does cross-repo impact analysis work for detecting breaking changes?▼

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.

What is the best way to assess deployment risks and rollback needs for a PR?▼

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.

Can I use this impact analysis skill for cross-repo scenarios and microservices?▼

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.

What artifacts do I need to provide for a comprehensive PR impact analysis?▼

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.

When do I need a dedicated risk assessment for breaking changes in a PR review?▼

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.