roborev:review

To automate a code review for a specific git commit, you can submit a background task that validates your input refs and executes a review on the given commit or HEAD. This process returns structured findings grouped by severity to guide issue resolution.

Yes, you can run a security or design focused code review by specifying an optional type flag when requesting the review. This focuses the automated background analysis on either security vulnerabilities or design flaws for your specified commit.

Background code review works by constructing a review command for a specific commit, executing it as a background task, and monitoring the process. It then reports the final verdict and structured findings without blocking your current development workflow.

The best way to view structured findings from an automated code review is through the generated results report. This report displays a final verdict alongside findings grouped by severity, providing navigation cues and actionable guidance for addressing each issue.

No, you do not need to specify a commit hash to run an automated code review. The review defaults to HEAD if no specific commit is provided, validating input refs automatically before executing the background task.