I am wondering how some people are against about a checklist of what a pull request should have before it can be merged / what a reviewer should be looking for when reviewing a PR.
Of course, all we are lazy humans. And we rather skip it at all than try to follow it up. But I think it's a problem of our attitude to this thing. Of course, this approach has own pros and cons. IMHO, the checklist reminds us about the important steps what we should do or check. It means better and more consistent code quality and helps to avoid breaking the rule of no surprises. Also, it's useful for new team members.
I am sure you will say, that a well-experienced developer should keep this list in mind all the time. But I am not talking about obvious things as use patterns, best practices: Single Responsibility Principle, KISS, DRY, SOLID, etc.
It could be something like that or even less: