code-review

To review a pull request for security vulnerabilities and performance issues, apply structured checks to the code changes for OWASP-Top-10 concerns, N+1 queries, and memory risks. This process surfaces critical defects before merging.

Auditing post-merge code changes for correctness involves identifying edge cases and error handling gaps, while maintainability checks assess naming conventions and readability. This skill provides a structured lens to evaluate ongoing quality and reduce audit risk.

You can use automated code review to detect N+1 queries and expensive operations by applying structured performance checks to file paths or diffs in your repository. This identifies memory risks and expensive operations to prevent defects.

Structured code review does check for OWASP-Top-10 security concerns and auth issues. It evaluates code changes for potential vulnerabilities and insecure patterns, ensuring security gaps are identified during pre-merge reviews or post-merge audits.

Analyzing a hotfix for error handling gaps and edge cases requires applying correctness checks to the specific files or diffs involved. This skill identifies missing error handling and edge cases to prevent defects in rapid code changes.