Review changes
After Aru edits files, review both the file list and the actual content. The task shows files changed during that conversation; Changes shows the current Git state of the repository.
Review files changed in a task
- Review the changed-file list in the response.
- Open a file.
- Compare the before and after content.
- Open the full file or ask Aru to explain anything unclear.
Explain why
src/login.tschanged and which existing behavior it may affect. Do not make any more changes.
Review changed code, values, and wording together with the actual runtime result.
Review Git changes
Open Changes in a Git project to see modified files and diffs. The list can include your own edits as well as Aru’s.
Staging selects changes for the next commit. Saving a file is not the same as committing it; review the changes and follow your repository’s process.
Revert changes
| Action | Scope |
|---|---|
| Revert file changes | Discards working-tree changes for that file. |
| Revert folder | Discards working-tree changes below that folder. |
| Revert all | May discard both staged and working-tree changes for the target files. |
Reverting can discard changes you made yourself. Untracked files may be deleted. Commit or copy anything you need before continuing.
Review the path and diff, confirm the scope, then inspect the list again. If some files fail, check the remaining Git state.
Conversation rewind is different
Rewind from here moves the conversation back. It is different from reverting Git files in Changes, and it cannot undo submitted forms or external-service actions.
After rewinding, inspect the actual file state in Changes. To explore another direction without losing the conversation, use Start branch from here and choose a worktree when files must also be isolated.