The work your team already does · 04 / Review

See what people or AI actually changed in the product.

Follow changes in business rules and product behaviour across processed commits instead of validating only the code diff in isolation.

WorkspaceMCP
What it is

Every time GitMir reads a repository it keeps a record of what the product does at that moment. The repository page lists those reads and shows what changed between any two of them: what appeared, what went away, what was renamed, and what now behaves differently. When the code moved but nothing about the product changed, it says so in words instead of showing an empty screen. The project page carries a shorter version — what changed since you last looked.

What you do
01

Open a repository inside a project

02

Pick a version from the list of reads and see it against the one before

03

Read what appeared, went away, was renamed or behaves differently now

04

Use the project digest for what changed since your last visit

05

Set up the push hook so the model is rebuilt on every push

What it does not do

It compares two reads of the repository, not two commits. Rebuild once a week and the comparison spans that week; commit-by-commit only happens if you set up the webhook that rebuilds on every push. It deliberately holds no lines, no file names and no code diff — it reports what changed about the product, so your existing code review, whether that is a person or a tool like CodeRabbit, still happens exactly where it happens today. GitMir does not approve or block anything.

See it on a real product.

Three models are published in full and open without an account. Ask one of them the question this page is about.