AI can make a Unity edit faster, but speed is only useful when the change remains understandable, reversible and testable. This checklist is designed for any AI-assisted Unity workflow — not for one specific tool.
Commit the current state, work on a branch, or keep a known-good copy before an assistant edits scripts, prefabs, materials or scenes. The fastest rollback is the one you prepared before anything broke.
A narrow task is easier to review than a broad rewrite. Prefer one bug, one component or one refactor at a time. Large "improve the whole system" requests make it harder to identify which generated edit introduced a regression.
Treat generated code like code from a new contributor. Check what actually changed: public APIs, serialized fields, namespaces, assembly references, event subscriptions, object lifetimes and hidden allocations.
A feature is not finished because the target error disappeared. Recompile, clear the Console, reproduce the original case and check for new warnings, exceptions or import errors.
Unity problems often live outside the C# file. Verify missing scripts, unassigned fields, prefab overrides, object names, hierarchy assumptions, colliders, layers, tags and material references after automated scene edits.
Passing compilation is only the first gate. Run the affected interaction in Play Mode, test the edge case that caused the task, then make a development build when the change touches runtime initialization, platform APIs, shaders, input, addressables or build-only code paths.
If generated code adds loops, searches, allocations, reflection, repeated GetComponent calls, asset loads or shader work, profile it on the target hardware. "Works" and "fits the frame budget" are different checks.
Do not paste passwords, private keys, payment credentials, customer data or code you are not permitted to disclose. Review the provider's current privacy and data-handling terms before sending proprietary project context.
Before merging, be able to answer four questions: what changed, why it changed, how it was tested, and how to roll it back. If you cannot explain those four things, the edit is not ready just because it was generated quickly.