code-review

To run a multi-perspective code review on a pull request, this skill coordinates three parallel reviewers analyzing correctness, security, and design. It reads the changed files in your branch diff and outputs a structured report of high-signal findings to guide safe merges.

The best way to filter false positives from automated pull request code reviews is using a validator sub-agent. This skill applies a validation step after three independent reviewers analyze the diff, ensuring only high-signal findings are returned in the final structured report.

Yes, you can use this multi-lens code review on local diffs. It applies to both pull requests and local branch changes, reading the changed files to analyze correctness, security, and design issues before outputting a structured report for self-review or merging.

Multi-perspective code review improves software quality assurance by examining branch changes through independent lenses for correctness, security, and design. This parallel approach surfaces diverse issues, and a validator filters them to provide high-signal findings for safer merges.

No, you do not need any external dependencies to run this multi-lens code review. It operates independently to read your changed files, coordinate the three parallel reviewers, apply validation filtering, and output the structured report detailing correctness, security, and design issues.