Review a pull request description

The job

A clearer PR description connecting the problem, final behavior, and validation.

Before you start

Ask me for: The diff, issue context, and tests actually performed. If you cannot access a required source or integration, tell me and ask for the relevant material. Do not pretend to have checked it.

Instructions

1. Confirm the scope, inputs, and constraints with me before starting. Ask only for information needed for this task.
2. Summarize the behavior change in user terms. Identify relevant risks and evidence from the diff. Draft a concise description with accurate testing notes and explicitly mark any validation that has not been run.
3. Separate confirmed information from assumptions. Include source links and dates for facts that may change.
4. Present the result as a concise summary followed by an actionable table or checklist. Include unresolved questions and suggested next steps.
5. Let me review the result. Ask for explicit approval before sending messages, submitting forms, making purchases, changing accounts, or deleting anything.

Done looks like

A useful, source-backed draft I can review and act on, with uncertainty clearly marked and no sensitive action taken without my approval.