---
name: pr-summary-pack
description: Assemble a reviewer-ready pull request summary pack with change highlights, verification notes, risks, and reviewer prompts. Use when preparing a PR, release note, or handoff that must explain implementation work clearly and accurately.
---

# PR Summary Pack

## When to use

- Use after implementation when the change needs to be explained to reviewers or maintainers.
- Use when a merge request needs more than a shallow bullet list.
- Use after `verify-evidence` if the summary must be especially tight and defensible.

## When not to use

- Skip before the implementation and verification work are complete enough to summarize honestly.
- Skip for private scratch notes that are not going to reviewers.
- Skip if the diff is still unstable and the summary would churn immediately.

## Workflow

1. Collect the objective facts from the diff, docs, config, and verification output.
2. Decide the audience and compress the explanation to what that audience needs to approve the change.
3. Separate what changed from why it changed and how it was verified.
4. Surface real risks, migrations, or rollout notes instead of burying them in the summary.
5. Draft the pack using `templates/pr-summary.md`.
6. Run a final evidence pass to ensure the wording does not overstate certainty.

## Output contract

- `why`: problem statement in reviewer-friendly language
- `what-changed`: major implementation changes
- `verification`: commands, tests, and results
- `risks`: residual risk, rollout notes, or follow-up work
- `reviewer-prompts`: the key questions the reviewer should answer

## Examples

- `Use $pr-summary-pack to package this completed feature branch for a GitHub pull request.`
- `Use $pr-summary-pack to turn these implementation notes into a reviewer-ready summary with verification and risks.`

## Resources

- Read `references/audience-matrix.md` when tailoring the summary.
- Use `templates/pr-summary.md` as the output structure.