code-review-expert

Reviewing git changes for security risks and SOLID violations involves analyzing your current diff to detect architectural smells like SRP/OCP/LSP/ISP/DIP violations and common web vulnerabilities. The process outputs severity-ranked findings from P0 to P3 with safe refactor recommendations before merging a PR.

Scanning a git diff for performance anti-patterns and boundary-condition bugs involves checking changed files against internal reference checklists to identify N+1 queries and error-handling failures. This yields prioritized code-quality findings and an incremental follow-up plan to ensure reliability.

A structured code review prevents production incidents by applying a senior-engineer style analysis to current git changes, focusing on correctness, security, reliability, and performance. It systematically surfaces race conditions, auth gaps, and secrets leakage before the code reaches production.

Yes, you can get safe removal and refactor guidance directly from commit changes by analyzing the diff for architectural violations. The review proposes safe deletion candidates and minimal refactors with verification steps, defaulting to review-only until you explicitly confirm the implementation.

Automated PR review covers reliability issues like race conditions and error-handling failures by scanning the git diff for runtime risks. It consistently applies internal checklists to produce severity-ranked findings and a structured next-steps plan for resolving these specific defects.