A coding assistant is easier to review when the request describes one observable outcome and the surrounding behaviour that matters.
Point it to the relevant function or component. Include a realistic input and the expected result. For a contact form validation change, explain what should happen with blank fields, a valid submission and existing saved data. Ask for the smallest edit that supports those cases.
Read the change before running it. Verify the normal path and the boundary that triggered the request, then check whether the assistant introduced new dependencies or configuration. Keep the example that exposed the issue so you can use it during review.