code-review-expert

To analyze git changes for SOLID violations and security risks, run the code review command to execute preflight checks using git status and git diff. The review surfaces architecture defects and vulnerabilities, outputting a structured markdown report with findings categorized by severity from P0 to P3.

The best way to review pull requests for maintainability is using an automated workflow that evaluates diffs against SOLID principles. It guides reviewers through architecture and security checks, generating a structured report with an optional remediation plan to prevent problematic merges.

Yes, you can get a structured code review report with severity levels for your current diff. The review evaluates git changes and outputs findings categorized by severity from P0 to P3, detailing security risks and quality issues alongside an optional remediation plan.

Yes, the code review process includes preflight checks using git status and git diff. These contextual diff analyses identify SOLID violations, security vulnerabilities, and quality issues before generating a structured markdown report to guide engineers through remediation.

Prevent problematic merges by identifying security vulnerabilities through an automated code review of your git changes. The process scans diffs for common reliability concerns and design defects, providing a structured markdown report with a remediation plan to resolve issues before integration.