Before a commit
Review staged changes with focus.
lurus code-review-ci --staged Code Review
Review architecture, security and performance before merging.
Review changes in context: architecture, security and performance. Get explainable findings, not just another opinion on style.
From diff to decision
Identify issues, explain their impact and recommend fixes.
- 01
Establish the context.
The change scope and project structure form the basis for analysis. Pre-checks such as linting and type-checking help separate mechanical issues early.
- 02
Review from different angles.
Architecture, security and performance are considered together – not just assessed line by line.
- 03
Put findings into perspective.
The structured report explains issues and makes next steps clear. You decide what needs to be resolved before merging.
Review reports in HTML, JSON or PR comments.
Use HTML for a readable report, JSON for automated processing or PR comments within your review workflow. Choose the output that fits the next step.
The right scope
Review staged changes, a branch diff or the full codebase.
Before a merge
Compare against a branch or commit.
lurus code-review-ci --diff-base main For an overview
Include the full codebase in the review.
lurus code-review-ci --full Run reviews locally and in your CI pipeline.
Start locally with a diff. Bring the same review into your pipeline when the process fits. Human review and tests remain part of your approval.
For Pro, Pro+ and Ultra. Paid subscription after the trial unless you cancel beforehand. Usage and features depend on your plan and credit.
AI reviews can miss issues or produce incorrect findings. They support your review – they do not guarantee correctness or a safe merge.
- Install the CLI
npm install -g @scramble-cloud/lurus-code-cli - Connect your account
lurus login - Before a commit
lurus code-review-ci --staged
Your code stays yours.
Source code and request context are processed with Zero Data Retention. No use for model training. Providers and processing regions are disclosed transparently.
See privacy and processing detailsA few things to know before you start.
Do I need to review the whole project every time?
No. You can choose staged changes, a comparison against a Git ref or the full codebase. The command reference covers each option.
Can I share results with my team?
Yes. HTML and JSON reports, as well as PR comments, support different review processes. For CI, use code-review-ci.
Can the review automatically decide whether a merge is safe?
A review provides findings and assessments, not a security or correctness guarantee. You define the approval rules and check relevant findings with your team.
Code Review
Before you merge: take a closer look.
Try a review on a real change. Start with staged files or a comparison against your target branch.
For Pro, Pro+ and Ultra. Paid subscription after the trial unless you cancel beforehand. Usage and features depend on your plan and credit.
Want to start with your team? Talk to us.