My team uses a github PR template with the following sections. Answers to each can be short yet it has been extraordinarily helpful to pass over important info to the reviewer that's not captured in code. It also borders on "checklist" that the code author has actually done the bare minimum to think things through.

# Goal (why is this change needed at all)

# What I changed and why I did it this way

# What I'm not doing here and how I'll follow up

# How I know it works (optional section, I include this only for teams with lots of very junior engs: "added a test" is often sufficient)