code-review

To review a pull request for security vulnerabilities and performance issues, apply static analysis to the diff to identify SQL injection, XSS, N+1 queries, and race conditions. You receive prioritized findings with file and line references, severity labels, and remediation steps.

Static analysis for finding bugs and security flaws is the process of reviewing code diffs or snippets to detect correctness errors, insecure deserialization, and SSRF. It yields prioritized findings with severity labels, specific file and line references, and actionable remediation steps.

Yes, you can use code review to detect performance regressions in individual files by analyzing them for expensive allocations, unbounded loops, and algorithmic inefficiencies. The review outputs prioritized findings with file and line references for developer consumption.

The best way to check a code snippet for maintainability problems before merging is to review the pasted snippet for poor naming, duplication, edge-case omissions, and test coverage issues. The process provides prioritized findings alongside positive observations to guide improvements.

Yes, code review works for finding auth and authorization flaws in diffs by flagging security vulnerabilities like CSRF and secrets. It outputs prioritized findings with file and line references, severity labels, and remediation steps to fix high-risk issues before production.

Automated code review for maintainability gaps is limited to detecting edge-case omissions, poor naming, duplication, and test coverage issues within the provided diff or snippet. It cannot assess architectural design flaws beyond the submitted code context and relies on the input boundaries.