jorgempenalva/pr-with-user-impact

Overview

This skill generates pull request content that clearly explains how code changes affect real users. It transforms technical diffs into concrete before/after workflow examples and emotionally resonant impact statements. Use it to make PRs, commits, and change descriptions that stakeholders can validate and act on.

How this skill works

Given a code change or diff, the skill identifies the affected user, the user’s goal, and the concrete pain experienced before the change. It produces a short User Workflow Impact section with a realistic before/after table and a concise impact statement that links emotional relief to business outcome. The output avoids technical jargon and keeps claims testable by interacting with the product.

When to use it

• Creating a pull request for a feature, fix, refactor, or infra change
• Writing commit messages for visible user-facing changes
• Preparing release notes that non-technical stakeholders will read
• Reviewing changes to confirm real user impact before merge
• Communicating cross-team impact to product, support, and design

Best practices

• Always name the user and their exact action (who does what)
• Use realistic details: times, counts, error messages, names, and category titles
• One scenario per workflow section—split multiple user types into separate sections
• Make claims testable: someone should be able to reproduce the before and after
• Use emotional relief language tied to a clear business outcome (reduced churn, faster decisions)

Example use cases

• Performance improvement: show dashboard load time before/after and the emotional impact on users
• Bug fix: demonstrate a silent failure before and a clear success message after for affected inputs
• Feature addition: show how a one-click export replaces manual CSV-to-Excel steps
• API change: replace a generic error with a structured message so developers fix issues faster
• Security/infrastructure: show how session warnings and autosave prevent lost work