code-review-expert

To review a pull request for SOLID violations and architectural smells, analyze the current git changes to identify structural issues, categorize them by severity, and generate actionable improvements for maintainability and correctness.

Checking git changes for security risks involves evaluating the diff to identify vulnerabilities, categorizing them by severity, and providing clear guidance with safe remediation steps to ensure correctness before merging.

Yes, this code review approach works across different programming languages and modules by analyzing the structural impact of git changes on SOLID principles, architecture, and security rather than relying on language-specific syntax rules.

To plan the safe removal and iteration of code with architectural smells, use structured workflow prompts that define risk levels, outline follow-up tasks, and provide clear guidance for safe remediation of the identified violations.

Predefined severity levels are needed in a pull request review to prioritize SOLID violations, architectural smells, and security risks accurately, ensuring that critical correctness and maintainability issues are addressed before minor improvements.

You should not rely on automated code review for your git diff when evaluating highly specialized domain logic, as the review focuses broadly on SOLID principles, architectural smells, and security risks rather than business-specific correctness.