Running it
When git reports local changes, a Git-changed files detected strip appears above the sidebar tabs. The count only includes files Iris Code will actually read: JavaScript, TypeScript, Vue, Svelte, Go, Python, Ruby, C#, Java and Rust. Click the strip, or run Iris Code: Review My Changes from the command palette. It opens in its own editor tab with:- a verdict at the top, “ready for review” or “needs attention”, blockers first
- filters by severity, and a search box
- a health score for each changed file
- click-to-open on every finding
Scoped honestly
A review of eleven files is not a review of the project, and the two are kept distinct:- No trend snapshot is created. A partial scan would distort your history.
- No unused-dependency conclusions. That requires scanning everything that might import a package.
- Untracked files are included, unless
.gitignoreexcludes them. - A workspace inside a larger repository reviews only its own changes. Opening one package of a monorepo never surfaces findings from a sibling package you did not touch.
iris check --staged in CI, and hook enforcement are Pro.
Real repositories
The awkward cases are handled deliberately rather than left to fail:- No git repository: the strip stays hidden and the command explains why rather than erroring.
- Git not installed: reported as exactly that, rather than as a missing repository.
- A new repository with no commits: staged and untracked files are still reviewed.
- Large untracked folders, paths with spaces or unicode, a merge in progress: all handled.