pr-impact-review

Review pull request diffs for user value impact and product quality from a PdM perspective.

1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/tktcorporation/cli-sim-game-escape --skill pr-impact-review-tktcorporation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-impact-review
Source: https://github.com/tktcorporation/cli-sim-game-escape/tree/main/.claude/skills/pr-impact-review
Command: npx skills add https://github.com/tktcorporation/cli-sim-game-escape --skill pr-impact-review-tktcorporation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Line-level code review tools check whether code is correct, but they cannot answer whether a PR should actually ship to users. This Skill evaluates PR and branch diffs from a product manager's perspective, judging user value changes, alignment with the issue's intent, and unexpected side effects so a PdM can make a go/no-go merge decision. ## Core Features & Use Cases - User Value Assessment: Analyzes before/after user experience changes, covering both gains and trade-offs, plus user-visible external spec changes (UI, behavior, responses, error messages). - Intent Alignment Check: Compares the actual diff against the issue or PR description to detect scope creep, under-delivery, or silent spec changes. - Pass/Fail Verdict: Produces a concise summary with a clear verdict (approve / conditional / reject) based on severity-rated concerns, translated into user experience terms. - Use Case: Before merging a feature PR, ask for a PdM-perspective review to confirm the change delivers the intended value, has no silent behavior changes, and is safe to release to users. ## Quick Start Review this PR from a PdM perspective and tell me whether it is safe to merge and how it changes user value.

Frequently Asked Questions about pr-impact-review

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

FAQPage Schema
How do I review a PR from a product manager perspective?

Fetch the PR description and diff with gh pr view and gh pr diff, then evaluate user value changes, alignment with the issue's intent, and unexpected side effects. Conclude with a clear approve, conditional, or reject verdict a PdM can act on.

What is the difference between code review and PR impact review?

Code review checks whether the code is correct at the line level, while PR impact review judges whether the change should ship to users. It focuses on user value gains and losses, intent alignment, and silent spec changes rather than code correctness.

How do I detect silent spec changes in a pull request?

Compare the diff against the declared intent in the issue or PR description and look for user-visible behavior changes nobody announced, such as default value, ordering, or UI shifts. Only flag changes users can actually perceive and that cause real disadvantage.

When should I not use a PdM-perspective PR review?

Skip it for internal refactors, typo fixes, or comment-only changes where user-facing value does not change at all. In those cases a one-line conclusion of no user value change is sufficient.

How are severity levels assigned to PR review concerns?

Concerns are rated Critical, Major, or Minor based on user impact: Critical covers data loss or wrong information driving decisions, Major covers visible malfunctions requiring fixes before merge, and Minor covers edge-case or cosmetic issues that can be deferred.