review-code

To get a structured code review for a pull request, provide the diff, commit, or staged changes. The review produces a report with a verdict, inferred intent, critical issues, suggestions, and a summary with file paths and line references.

Yes, you can adjust code review depth to match project risk. Choose Quick, Standard, or Deep review depths to evaluate correctness, readability, and project fit based on the potential impact and scope of the changes.

The best way to avoid bias when reviewing your own code commits is to spawn an isolated reviewer teammate. This team isolation workflow preserves a repeatable review process and provides objective, bias-free evaluation of your work.

This code review tool works with both individual files and branch diffs. You can apply targeted evaluations to pull requests, commits, staged changes, or specific files when you request an assessment rather than implementation.

A code quality evaluation report includes categories for Critical Issues, Suggestions, and Questions. It also provides a clear Verdict, Inferred Intent, and a concise Summary with specific file paths and line references.

You should use a deep code review instead of a quick scan when the scope, risk, and potential impact of the changes are high. Depth-matched analysis ensures the review effort aligns with the project's correctness and quality concerns.