petrvs-code-review

To review Laravel and Angular code changes for security vulnerabilities, analyze pull request diffs for mass assignment risks, data exposure, and missing sanitization. This process checks authorization, validation, and guard usage to pinpoint security issues before merge.

The best way to detect N+1 queries and inefficient RxJS subscription patterns is to perform a diff-based performance review across the Laravel and Angular stacks, identifying database query bottlenecks and problematic front-end rendering or subscription logic.

To check if your pull request meets architecture standards for Services, Repositories, and SOLID principles, validate the diff against established quality alignment patterns. This ensures Eloquent Resources and front-end structure conventions are correctly implemented.

Yes, you can use an automated review to assess sensitive authentication and permission modifications in a Laravel backend. Pre-merge analysis evaluates the modified API calls and authorization logic, organizing findings by risk severity and referencing affected files.

You should run a diff-based code assessment on critical modules immediately after sensitive authentication, permissions, or query modifications, and before merging any pull request. This ensures safety and efficiency requirements are covered before changes ship.