I doubt that "Verify feature requirements ✔️" should be part of the code review. This is something to be verified by the demo to the product owner, but of course your workflow may differ.
"Coding Style 💅" should be automated as much as possible, in practice, with the right tools, this can be done by a machine. If you still discuss about code style in CRs you are not automating enough.
" Tests ✅ You should always check that the implemented tests cover all coding paths. Make sure to flag any missing tests to the PR owner." Again that is a job for a machine - automate this away, you'll have enough work with checking that the tests make sense and testing the right thing, the right way.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I doubt that "Verify feature requirements ✔️" should be part of the code review. This is something to be verified by the demo to the product owner, but of course your workflow may differ.
"Coding Style 💅" should be automated as much as possible, in practice, with the right tools, this can be done by a machine. If you still discuss about code style in CRs you are not automating enough.
" Tests ✅ You should always check that the implemented tests cover all coding paths. Make sure to flag any missing tests to the PR owner." Again that is a job for a machine - automate this away, you'll have enough work with checking that the tests make sense and testing the right thing, the right way.