review-code

To review a pull request for security vulnerabilities and logic errors, provide the PR patch or diffs along with a short goal description to generate a concise, prioritized review checklist with concrete remediation steps.

The best way to structure code review feedback for maintainability is to use a What, Why, and How format that explains the issue, its architectural impact, and proposed concrete remediation steps with clear priority labels.

Yes, you can use automated code review to check edge cases and input validation across languages by applying the review process to pull requests and commits, validating logic, null handling, and robust error handling.

To assess architectural concerns and single-responsibility adherence in a code diff, evaluate abstractions and test coverage during the review to ensure long-term health and maintainability of the codebase.

Yes, this code review approach works for commits as well as pull requests, applying security-focused evaluation, correctness checks, and maintainability assessments across both types of code changes.

A limitation of using a structured checklist for code review is that it requires providing the PR patch or diffs and a short description of the goal to generate accurate, prioritized feedback and proposed remediation steps.