Automated assistants touch more files than the ticket mentions. A short review routine keeps the fix and drops the surprises.
An assistant that is asked to fix one failing test will often also tidy imports, bump a dependency or rewrite a helper it considers unclear. Each change may be harmless. Together they make a diff that nobody on the team asked for and few people read closely.
Read the diff, not the summary
The summary an assistant writes describes what it intended to do. The diff describes what it did. Open the diff first, sort it by file, and look for files that have nothing to do with the original ticket.
What to look for
- Changes to build, CI or deployment files that the ticket did not mention.
- New or upgraded dependencies, including lockfile entries.
- Edits to authentication, permission or input-validation code, even when they look cosmetic.
- Tests that were deleted or loosened so that they pass.
Make the safe path the easy path
Give the assistant a branch and no direct access to the main one. Require the same review and the same checks as for a human contributor. If a change touches a sensitive directory, route it to someone who owns that directory.
None of this is specific to one tool. The habit is the point: treat generated changes as a pull request from a fast, confident colleague who has not read your threat model.



