multi-perspective-code-review

You initiate a multi-perspective code review by specifying the command and optionally targeting a specific file path or module directory to analyze all changes within that scope.

A multi-perspective code review covers six dimensions: UI/UX accessibility and responsiveness, rendering performance, architecture scalability, code readability and conventions, edge cases, and security vulnerabilities.

Yes, you can target a specific module directory by appending the path to the review command, restricting the evaluation scope to only the files and changes within that specified tree.

Yes, the code review process explicitly checks performance by evaluating rendering, memory usage, and network calls, and identifies security vulnerabilities through a consistent risk taxonomy.

Use a multi-perspective code review during pre-PR stages to validate feature implementations or post-implementation to conduct structured retrospectives on quality assurance across your changed files.