code-reviewer

Automate pull request reviews using an 11-step protocol that systematically checks code for context understanding, naming conventions, cyclomatic complexity, SOLID principles, error handling, test coverage, DRY violations, documentation, performance, architecture fit, and web-specific patterns to ensure high code quality and security.

Yes, you can run security audits and accessibility validation on React and Next.js code. The review process includes supplementary checks specifically tailored for web and mobile accessibility standards alongside framework-specific patterns for ReactJS, Next.js, and React Native applications.

The best way to check Rails migrations and test coverage before merging is to apply a systematic review protocol that evaluates DRY violations, error handling, and framework-specific Rails checks to ensure the codebase meets project standards and maintain high software quality.

Yes, the code review process explicitly checks for cyclomatic complexity and SOLID principles. It evaluates code against multiple criteria including naming conventions, error handling, DRY violations, and performance to ensure strict adherence to software engineering conventions.

You need to run an automated code review on your pull request before merging to identify potential security vulnerabilities, verify test coverage, check architecture fit, and ensure the new code adheres to team conventions across multiple frameworks like Rails, ReactJS, and Next.js.