code-review-expert

To review a git diff for structural regressions, provide the branch comparison or commit range to surface security risks and maintainability issues before merging the pull request into production.

Catching architectural boundary leaks in a pull request requires analyzing the git diff context and repository structure to identify spaghetti growth, unnecessary wrappers, and missed code simplification opportunities.

Yes, you can use a code review tool to flag auth gaps, unsafe data access, swallowed errors, and race conditions by applying engineering judgment to the visible production risks in your branch diff.

Diff-focused code review separates critical structural and security issues from low-value nits by surfacing high-conviction findings specifically from changed files within the specified commit range.

Yes, you need repository structure awareness to review hot code paths in a commit range, as understanding architectural boundaries is required to apply correct engineering judgment about coupling and reliability.

You should not use automated git diff analysis alone when a code review requires deep runtime context or testing, as diff-visible production risks only cover structural, security, and maintainability boundaries.