AURA Code: review an agent edit before accepting it

A coding assistant is most useful when the change has a clear boundary. AURA Code provides a development workspace with agent edit approval and test-file generation flows. Treat each proposed edit as a change that still needs review.

Describe one observable change

Explain the current behaviour, the desired behaviour and the part of the project involved. Include a small example that a reviewer can reproduce. For instance, a form task might say which field should show an error and when the error should disappear.

List the files or areas the task is expected to affect, while allowing the agent to explain why another file is necessary. Separate the requested change from unrelated cleanup so the resulting edit stays reviewable.

Inspect the proposed edit

• Read the changed code and check that it solves the original case.
• Look for changes to permissions, secrets, network requests and dependencies.
• Check whether the new behaviour fits the existing project conventions.
• Ask for an explanation of any change whose purpose is unclear.

Approve an edit only when its scope is understood. An edit receipt tells you that a file operation succeeded; it does not show that the application behaves correctly.

Use tests as evidence

Run the project’s relevant checks and inspect their actual output. A generated test file must itself be reviewed, and then executed in the correct environment. A test that repeats the implementation without checking the user-visible behaviour offers little confidence.

Record the command, result and any limitation, such as a dependency that could not be reached. Mock conversations or simulated worker results should not be counted as successful builds. Keep the approved change and its verification together so another developer can understand what was checked.

Explore AURA Code

Visit the official AURA Code product page for current access and available features. Use Global IETA product guides to explore the connected ecosystem.