Ask the agent to explain its own changes and to point out what it's unsure about. Good tools will flag assumptions and edge cases they didn't handle. Push back and ask for tests covering the risky paths.
The discipline that matters most: understand the code before it ships. If a change is too large or unclear to review properly, break the task into smaller pieces the agent can do one at a time.
Updated July 2026