Right now, if Clayton gets something wrong, we need to go out of our way to inform Clayton what to ignore and which findings were defective.
A better workflow would be such that I might reply directly to Clayton’s with a review comment like
@Clayton, wrong: this method is required by an interface.
@Clayton, ignore: this is legacy code.
… where “wrong” and “ignore” would be keywords that give instructions to Clayton and everything afterwords is comment.
Additionally, if I make a comment
Clayton would rely something like:
Sorry but I don’t understand. These are there commands I recognise…