Receiving Code Review

Review feedback is technical input to evaluate, not a command stream to obey. Do not chase perfection: apply feedback that makes the change safer, clearer, or better aligned with the contract; push back on feedback that is wrong, speculative, or not worth the complexity it adds.

doing-code-review
  -> findings or reviewer comments
  -> receiving-code-review  (you are here)
       -> verify and classify feedback
       -> focused fixes / documented pushback / clarification
       -> focused verification
       -> doing-code-review          (if fixes are non-trivial)
       -> verification-before-completion