Open the PR your reviewer has not met yet

Short summary

Write PR descriptions for reviewers unfamiliar with your code. Structure them around intent (why this exists, not what changed), separate major architectural decisions from cleanup noise, map the blast radius, list what was tested, and explicitly name uncertainties. Treating the description as a pre-review checkpoint rather than a post-code summary forces deeper understanding and gives reviewers a focused map.

• •PR descriptions are a test of whether you understand your own code before asking others to review it
• •Structure: Intent, Major Changes, Minor Changes, Impact, Evidence, Uncertainties—each serves a distinct purpose
• •Write as if for a reviewer meeting your code for the first time with no memory of your context

Generated with AI, which can make mistakes.