Review code

Review uncommitted changes#

A commit records changes in Git. Run this from a Git project folder to review uncommitted changes in tracked files:

mirr review

This includes staged and unstaged changes, but not new files that Git does not yet track. If there are no changes, the command prints No changes to review.

Review against a branch or commit#

If the project's base branch is main, for example, run the following. Replace it with your actual base branch name when different.

mirr review --base main

This compares changes from the branches' common ancestor through the current commit. It does not include uncommitted edits. To review the most recent commit alone, use:

mirr review --commit HEAD

Add criteria in conversation#

Inside Mirr Code, describe the scope you want reviewed:

Review the login changes.
Prioritize regressions in existing login methods, authentication error handling, and missing tests.
Include file locations, impact, and evidence for each issue.

A useful finding explains when a problem occurs, rather than merely summarizing the change. For example: “An empty email throws an exception, and no test covers that case.”

After the review#

You can ask for fixes in the same conversation. AI review does not find every bug, so important changes still need tests and human review. See Implement a change for implementation and verification together.