code-review

To review a git diff for security vulnerabilities and bugs, paste the diff or provide a commit range to establish the scope, then analyze correctness, security, performance, and maintainability issues using the changed files as context.

Automating pull request reviews for maintainability involves analyzing the input diff, gathering context across affected files and dependencies, and producing prioritized findings structured by severity levels like P0 or P1.

Yes, you can use a commit hash to check code changes for performance issues by extracting the diff from the specified git commit and evaluating the modified implementation behavior against your stated requirements.

Code review works with git ranges by extracting changes across the specified range, gathering context from affected files, and validating modified implementation behavior against your specific requirements to ensure correctness.

Prioritize feedback when reviewing a code diff by classifying findings into severity levels from P0 to P3, requesting changes only for critical P0 and P1 fixes while treating P2 items as suggestions.

Shallow diff analysis misses correctness bugs because it lacks the context of full changed files and their callers, leading to misleading feedback instead of accurate severity classification and requirement-driven validation.