Your first review. Step by step.

From a task and selected MR to your team’s decision.

Sign in to your organization

Your administrator provides the private backoffice URL and a role. Sign in through corporate SSO and check your organization and allowed repositories. The public null.review website is not that backoffice.

Prepare the review

  • Select the GitLab connection, MR and current SHA. Add the task and acceptance criteria.
  • Inspect the diff, selected files, instructions and context before sending it to the model.
  • Choose an approved model profile, rules and allowed checks.
  • Start the review with explicit consent. Inspect queue status and the reason if a run is refused.

Read the result

A useful finding names the risk, evidence in the code and a recommendation. Read the AI response, test results, criteria coverage and SHA freshness separately. Zero findings do not prove task completion. INCONCLUSIVE means there is insufficient evidence for the overall decision.

After a fix

A new SHA gets new context and a separate review. Do not publish an outdated decision or automatically replay a publication with an unknown outcome. Inspect the saved report and MR state. Approve requires sufficient current checks; merge remains a separate team action.

Inspect recorded MR3