create-pr

To write a PR description that communicates user value, use a structured template that highlights user benefits, outlines testing expectations, and links to related Linear tickets to streamline reviews for frontend changes.

A pull-request body for UI updates should include a structured narrative of user benefits, reference related Linear tickets, and attach screenshots before submitting to ensure reviewers can visually verify the changes.

Yes, you can use this structured PR template for cross-cutting improvements as it enforces a value-driven narrative and clear testing expectations, reducing miscommunication and speeding up reviews across cross-team changes.

The best way to structure a pull-request description is to enforce a consistent template that focuses on user benefits, documents testing expectations, and prompts for screenshots when UI changes are included to reduce miscommunication.

You should link related Linear tickets when writing a PR description for cross-team changes to guide alignment with project processes and provide reviewers with direct context for the value-driven updates.

Your PR template requires screenshots for UI updates before submitting to provide visual verification of the user-focused changes, ensuring reviewers can accurately validate the frontend improvements and user benefits.