How Reed reads a pull request

What he reads

When a pull request is opened or marked ready for review, Reed is given its title, its description and the diff of the changed files, with your README for context. Draft pull requests are left alone until they are ready.

What he writes

A note in four parts: what this changes, risks, missing tests, questions. A part is left out when there is nothing real to say in it. He only points at things that are visible in the diff.

What it is not

It is a first pass for the maintainer, and the note says so. Reed does not approve, request changes or merge, and he posts one comment, not a line-by-line review.