```
As a developer
I want to get better at making my PRs easier to review
So that they get reviewed sooner and I can merge faster => shorter cycle times

As a code reviewer
I want PRs that are easier to review
So that it's less work
```

I wish to claim that spending extra time as developers on writing PRs is repaid in time saved by the people reading them - if only because they are read more often than written.  Here are some of the things I now try and remember to put in on each one.  Obviously not all points are relevant to all changes in all projects.

I would like to hear your opinions: as a reviewer, are there other things you would really like to see in PR messages that you don't, or are there things I'm proposing to write here that you really don't think are valuable to read?  As a contributer, does this seem too little/about right/too onerous?