···2121[Process](https://github.blog/2015-01-21-how-to-write-the-perfect-pull-request/):
222223231. Include the purpose of the Pull Request.
2424-1. Provide an overview of why the work is taking place.
2525-1. Be explicit about what feedback you want, if any: a quick pair of :eyes: on the code, discussion on the technical approach, critique on design, a review of copy.
2626-1. [Offering feedback](https://mtlynch.io/human-code-reviews-1/)
2424+2. Provide an overview of why the work is taking place. Give a good background on why the change is happening.
2525+3. Be explicit about what feedback you want, if any: a quick pair of :eyes: on the code, discussion on the technical approach, critique on design, a review of copy.
2626+ - [Explicitly list how to perform validation](https://www.brautaset.org/posts/levelling-up-pull-requests.html).
2727+4. [Offering feedback](https://mtlynch.io/human-code-reviews-1/)
2728 1. Familiarize yourself with the context of the issue, and reasons why this Pull Request exists.
2829 1. Ask, don't tell.
2930 1. Explain your reasons why code should be changed.