Meet the emotion engine
Skip to content
FoxoraFoxora
Foxora Docs
Browse documentation

Files & Editor

Reviewing changes

Review both the live editor buffer and the repository diff so unsaved text, agent edits, and Git changes are not confused.

View Markdown

Published Studio guide. Some screenshots show earlier versions.

On this pageSteps Expected result
Reviewing changes
Studio interface in English. Sample data.

Steps

  1. Check each edited tab for a dirty indicator and save or discard it deliberately.
  2. Use View changes in the editor to compare the file with Git HEAD when available.
  3. Run git status and git diff in Terminal to include untracked and cross-file changes.
  4. Run the project’s focused tests before accepting or committing.

Expected result

You can name every changed file, understand its diff, and cite the check that passed.

Note: View changes is a comparison with HEAD, not a staging or commit control.