> Spot bugs. Bugs and desired behavior should be covered by automated tests. The developer is the first responsible person for this topic. Spotting bugs in PRs

> Spot bugs. Bugs and desired behavior should be covered by automated tests. The developer is the first responsible person for this topic. Spotting bugs in PRs literally means spotting what bug exists despite the tests. A lot of the time a bug is coming from weak specification or misunderstanding of the specification. If the developer (and therefore the code) assumes that all addresses must have a postal code then the fact that people might not have a postal code is a bug present in the code. It will fail under circumstances the developer obviously didn't think about. The most difficult job for the developer is finding the holes in the specification.