code-reviewer

To check a pull request for security vulnerabilities, apply a security-first review workflow that identifies injection, XSS, CSRF, SSRF, IDOR, and path traversal patterns, alongside verifying authentication and authorization logic to ensure changes are safe for merge.

The best way to automate code quality checks is applying structured criteria that evaluate single responsibility, DRY principles, error handling, type safety, and naming conventions, which systematically reduces long-term maintenance costs across multiple project structures.

Detect performance regressions and N+1 database issues by applying performance heuristics during code review that flag inefficient algorithms and problematic database usage patterns within the proposed changes before they reach production.

Yes, you can use static analysis to verify test coverage by evaluating proposed changes for sufficient coverage, edge cases, and error scenarios, ensuring robust testing validation before approving merge requests.

A pre-merge code review ensures documentation validation by checking that public APIs and complex logic are properly documented, and by producing constructive, prioritized feedback templates to communicate missing changelog entries.

When evaluating code changes for correctness and maintainability, review security vulnerabilities first, then proceed through quality, performance, testing, and documentation phases to ensure comprehensive pre-merge assurance.