code-review

To check code changes for security vulnerabilities, you need a code review that analyzes your git diffs for injection risks, data exposure, and auth bypasses. This process identifies potential security flaws before merging.

The best way to identify performance issues like N+1 queries is through a performance review. This code review process examines your code diffs to detect inefficient patterns and blocking operations.

Yes, you need git to run this code review because the Skill requires git diffs to obtain your code changes. It uses these diffs to perform comprehensive checks for correctness, security, performance, and maintainability.

Yes, you can use this code analysis tool with various programming languages. It is designed for developers seeking expert analysis of code correctness and maintainability across different language ecosystems.

To review specific commit code changes for maintainability, provide the commit hash to the code review process. It assesses readability, naming conventions, and the overall structure of the code in that diff.