review

To perform a code review on uncommitted git changes, provide the specific files or staged changes. The review checks correctness, security, performance, and quality, returning file:line issues with fix suggestions.

The best way to check code quality before merging is to assess correctness, security vulnerabilities, and performance bottlenecks. This process reports actionable file:line issues with concrete fix suggestions or returns PASS if criteria are met.

You can review the most recent git commit for security vulnerabilities if no uncommitted or staged changes exist. The review identifies vulnerabilities, validates logic, and checks error handling, providing file:line references for fixes.

To get actionable fix suggestions for performance bottlenecks, provide your code changes for an in-depth assessment. The review identifies bottlenecks and returns a concise list of file:line issues with concrete fix suggestions to guide developers.

The code review process validates edge cases and error handling through correctness checks. It examines logic, identifies security vulnerabilities, and reports overall code quality issues with specific file:line references and fix suggestions.

You should use an automated code review when you need to thoroughly examine code changes for correctness, security, performance, and overall quality before merging. It provides actionable file:line issues and fix suggestions or returns PASS.