roborev:design-review-branch

You can automate a branch-wide design review by submitting a background task that evaluates every commit on the active branch, aggregates the findings, and returns a consolidated Pass or Fail verdict with actionable next steps.

A branch design review evaluates the architectural and design choices across all commits on a development branch. You need one when you want a consolidated design verdict and grouped findings before merging your code changes.

You can specify a base branch by providing the base parameter when invoking the review command. The system validates this input, launches the background review against that reference, and presents the structured results.

Yes, the design review workflow runs asynchronously in the background. It launches a background task using roborev so you can continue development while it prepares the verdicts and findings.

After the review completes, you receive a structured report displaying a clear Pass or Fail verdict, grouped findings from the branch commits, and suggested next steps to address any design issues.

No, the design review branch automation operates without external dependencies, using the built-in roborev background process to validate inputs, launch reviews, and present the final aggregated findings.