Okay, the model just gave you this code. What do you do before you accept it?
A strong answer treats the accept as taking ownership, reads the diff in a fixed order, and can name the things that get a diff rejected on sight
Before I accept anything I read the whole diff and make sure I understand what it's doing. If I can't explain it, I don't accept it, simple as that. I check that it handles errors and edge cases, that it matches our codebase conventions, and that any APIs it calls are real and used correctly. Then I run the tests, or write a quick one if nothing covers the change, and I only build on the code once it passes. If a piece is unclear I'll ask the model to explain it or simplify it. My rule is basically to assume nothing about generated code and verify everything that matters. The speed of generation should never push code through faster than I can actually evaluate it.