code-review-expert

Reviewing git diff for SOLID violations is done by checking current changes against SRP, OCP, LSP, ISP, and DIP rules to detect design smells and propose minimal, safe architectural improvements.

Identifying security vulnerabilities in a pull request involves scanning security-sensitive modules within the git diff to detect potential risks, authentication gaps, and reliability issues for a prioritized remediation plan.

Automated code review assesses error handling and performance by flagging error handling gaps, performance hotspots, and boundary condition risks directly within the current git changes.

This code review approach works directly with standard git changes and pull requests, analyzing the active diff across architecture, security-sensitive modules, and performance-critical paths to output an actionable report.

Generating a prioritized remediation plan from a code diff requires evaluating the changes for architecture, security, and code quality issues, then formatting the findings into a structured, actionable report ready for developer action.