How can AI review uncommitted code changes?

How can AI review uncommitted code changes?

AI can review uncommitted code by inspecting the working tree and comparing the intended changes with the existing application. The review should have a specific objective: identify defects, security problems, regressions, or missing requirements introduced by the current increment.

Define the exact material under review

Start with the repository status. Unstaged changes and staged changes are different views: Git exposes them through ordinary diff and cached diff comparisons. New untracked files also need separate inspection because they are not automatically included in those comparisons. Git diff documentation.

Give the reviewer the task requirements and identify unrelated local edits. Ask for review before modification so the reviewer can establish what behavior exists and avoid quietly changing the evidence it is evaluating.

Follow changed behavior across boundaries

For wedding-event editing, reading the form alone is insufficient. Trace the request through validation, membership checks, database updates, and the refreshed dashboard. Check what happens when a collaborator submits another wedding's identifier or a save request fails.

The reviewer should examine relevant surrounding code, not only lines highlighted in the diff. A new field may conflict with an existing schema, and a reused helper may have assumptions the changed caller violates.

Produce findings that can be verified

A useful finding names the affected location, the triggering condition, the resulting incorrect behavior, and a practical correction. For example: “A failed event save closes the dialog, so the organizer loses their input before seeing the error.”

Distinguish confirmed problems from questions and optional styling preferences. Reproduce significant findings when the available environment permits it. If tests are run, report the actual result and any missing coverage.

After a fix changes the reviewed code, inspect the affected path again. An earlier clean review applies to the earlier code, not automatically to the final commit.