review

To run a code review on a git diff, you can execute a five-pass analysis focusing on changed hunks and contextual lines. This identifies correctness, security, performance, readability, and consistency issues, reporting exact file paths, line numbers, and concrete remediation steps.

A five-pass code review systematically analyzes source code through Correctness, Security, Performance, Readability, and Consistency passes. This structured methodology surfaces logic errors, injection risks, and convention drift that automated linters and unit tests often overlook.

You can audit a directory by running a recursive five-pass code review that skips generated artifacts. It detects security vulnerabilities and performance regressions, yielding a final PASS, CONDITIONAL, or FAIL verdict with grouped findings and severity counts.

Yes, you can apply a five-pass code review to a single file for pre-commit checks. It evaluates the file against all five passes, outputting actionable findings with severity levels, concise code snippets, and specific fixes to catch defects before merge.

The best way to catch convention drift and logic errors is a structured five-pass code review. By grouping findings by pass and severity, it delivers precise, located, and actionable remediation steps for defects that automated tests often miss.