code-review

To perform a comprehensive code review, gather context using git diff and git log, then execute a multi-dimensional review assessing correctness, security, performance, reliability, and maintainability to generate an actionable remediation report for your pull request.

Checking code changes for security and maintainability issues is done by applying a structured multi-dimensional review protocol with explicit checklists that evaluates diffs across these specific dimensions to ensure standardized actionable output.

In code review, the specialist consultation phase works by escalating complex findings identified during the multi-dimensional assessment to subject-matter experts, ensuring difficult correctness or security issues receive targeted evaluation before generating the final report.

You can use this structured code review protocol across different repositories because it applies to diffs, pull requests, and code changes universally, guiding reviewers through standardized formal checks regardless of the specific repository source.

Before starting an automated code review, you need to obtain the changes to review by running git diff and git log on the target files to provide the necessary context for the protocol's initial context gathering phase.