Running a review
When Git reports local changes, Iris Code shows a Git-changed files detected strip above the sidebar tabs - the count only includes files the review will actually analyse (JavaScript, TypeScript, Go, and Python). Select the strip, or run Iris Code: Review My Changes from the Command Palette. The review opens in a dedicated editor tab with:- a readiness summary (“Your changes are ready for review” / “need attention”) with blockers first
- severity filters and search across every finding
- per-file health for each changed file
- click-to-open on every finding, straight to the affected line
Scoped honestly
A partial scan must not pretend to be a full one:- A change review never creates a workspace trend snapshot.
- It never reports unused dependencies - that conclusion requires scanning the whole project.
- Untracked files are included only when
.gitignoredoes not exclude them. - A workspace opened inside a larger repository (a monorepo package, for example) reviews only the workspace’s own changes - never sibling changes elsewhere in the repo.
iris check --staged / --changed in CI, and hook enforcement remain Pro.