code-review-expert

Review code changes for SOLID violations and security risks by evaluating diffs against established checklists. This process identifies architectural flaws, vulnerabilities, and performance issues, producing severity-scored findings to prevent costly rewrites.

Static analysis for code review detects misconfigurations and data leakage by scanning source code without execution. It applies security and reliability checks to identify vulnerabilities, race conditions, and architectural issues across pull requests.

Check SOLID principles in a pull request by applying SRP, OCP, LSP, ISP, and DIP architectural guidance to the diff. This evaluates code changes against design checklists to generate severity-scored findings and an actionable iteration plan.

Identify removal candidates in git changes by analyzing the diff for redundant or unsafe code. This generates a safeguarded refactoring plan and actionable recommendations to improve architecture and eliminate reliability concerns.

Yes, this code review approach works directly with raw git diffs and pull requests. It evaluates the changes by referencing SOLID, security, and code-quality checklists to produce severity-scored findings and an iteration plan.

Static analysis for detecting race conditions has limitations when evaluating complex runtime concurrency behaviors. It excels at identifying architectural and data leakage risks in diffs, but dynamic analysis may be needed for verifying runtime reliability.