code-review-large

To review a large pull request, systematically assess architecture concerns, performance bottlenecks, and security vulnerabilities aligned with OWASP, generating a comprehensive risk and maintainability report for codebases exceeding 500 lines.

Identifying design pattern violations in large pull requests requires an architecture assessment that evaluates structural flaws and maintainability issues, providing recommended fixes to reduce the risk of defects in extensive code changes.

Yes, you can assess breaking changes and performance bottlenecks in PRs over 500 lines through thorough risk assessment, applying end-to-end code review workflows that output documentation alignment checks and optimization recommendations.

Checking technical debt and maintainability issues in a massive code change involves evaluating readability and architectural flaws, producing a thorough code review report that highlights potential breaking changes and documentation gaps.

You need an end-to-end code review for a large PR when changes exceed 500 lines and span multiple domains like architecture, performance, and security, requiring thorough risk assessment and recommended fixes to prevent defects.