pr-description

name	pr-description
description	Writes clear pull request descriptions from diffs, commits, or implementation notes, including summary, motivation, testing, risks, and rollout.

PR Description

Use this skill when preparing or improving a pull request description.

Inputs

• Diff, changed files, commits, branch name, issue links, or implementation notes
• Test results or validation steps
• Any rollout, migration, or risk context

Steps

1. Read the diff or change summary and identify the user-facing and technical purpose.
2. Separate what changed from why it changed.
3. Identify tests run, tests not run, manual checks, and any observed limitations.
4. Surface risks, compatibility concerns, migrations, rollout steps, or follow-up work.
5. Keep the description concise enough for reviewers to scan.

Output

Provide a PR description with:

• Summary
• Changes
• Testing
• Risks / rollout
• Screenshots or artifacts section when relevant
• Linked issues or follow-ups when known

Guidelines

• Do not overstate test coverage.
• Prefer concrete bullets over marketing language.
• Mention user-visible behavior changes explicitly.