review

To automate GitHub PR reviews, provide the owner/repo and PR number to receive a multi-perspective assessment. The review covers security, performance, quality, and documentation in parallel, returning blockers, suggestions, and a merge decision.

You can restrict a pull request review to specific domains by passing the focus parameter with values like security, performance, QA, docs, or types. This constrains the analysis to your chosen area instead of evaluating all domains.

The best way to get a merge decision is to run a multi-perspective PR review. It evaluates code quality, performance, tests, and security in parallel, then outputs a formal merge decision alongside blockers, suggestions, and nice-to-have items.

Multi-angle code review works for analyzing documentation and types. The review skill assesses pull requests across five domains, including docs and types, to identify blockers and opportunities for faster merges.

To get actionable suggestions for GitHub PR blockers, run a parallel multi-perspective review. The output categorizes findings into Blockers, Suggestions, and Nice-to-have items, ensuring maintainers receive clear guidance for merging.

Automated PR review limitations include requiring a valid owner/repo and PR number to function. While it provides a formal merge decision, the assessment is constrained by the specified focus areas and does not cover domains outside its five supported categories.