roborev:design-review

To obtain an automated design review for a specific commit, invoke the skill with your target commit hash. It launches a background process using roborev review to validate the commit and returns a formal verdict with severity-grouped findings.

Yes, you can run an asynchronous code review in the background. The skill launches the review process asynchronously, allowing you to continue working while results are prepared, and then surfaces the design-review verdict when complete.

Design review findings are presented grouped by severity, including references to affected files. The results include a formal design-review verdict and suggest follow-up actions to address any identified issues via the address workflow.

No, you do not need to specify a commit hash to validate repository changes. The design review process applies to individual commits or defaults to HEAD in a repository if no specific commit is provided.

After receiving a design review verdict, the suggested follow-up action is to address findings via the address workflow. This allows you to systematically resolve severity-grouped issues and references to affected files returned by the review.