code-review

To detect requirement drift during a pull request review, evaluate changes against original requirements intent, architecture boundaries, and test coverage. This process flags divergences between implemented changes and intended designs before merging.

Assessing merge readiness for high-risk refactoring involves analyzing code organization, performance implications, and resource usage. This evaluation provides actionable blockers and improvement recommendations sorted by risk level.

Evaluating code maintainability and elegance in a diff review requires checking readability, style consistency, and architecture boundaries. This assessment ensures long-term code quality and prevents structural drift.

Yes, an automated code review can check performance regressions and test coverage by analyzing resource consumption and boundary conditions. It identifies risk flags and provides actionable improvement recommendations.

To trigger a strict code review assessment, you need to provide the pull request link, commit range, and background context. This input allows the evaluation of requirements intent and architecture boundaries.