code-review

To identify security vulnerabilities and code quality issues in a pull request, apply a security-first checklist covering hardcoded secrets, input validation, parameterized queries, and path traversal prevention. Produce structured feedback with actionable issue descriptions, severity levels, and suggested fixes.

Reviewing large code rewrites and legacy code audits requires applying a comprehensive review checklist to scenarios with extensive changes. This process flags maintainability concerns, DRY violations, and insecure patterns while providing constructive, structured remediation guidance for improved software reliability.

Enforcing best practices and maintainability standards during a code review involves checking for proper error handling, clear module responsibilities, and adequate documentation. It also flags code smells and DRY violations to ensure long-term software reliability and safety.

Formatting code review feedback to be constructive and actionable requires using a predefined Review Response Format. This structure ensures each issue includes a clear description, severity rating, and suggested fixes, following established tone guidelines for constructive developer feedback.

Code review works effectively for both small patches and large code changes. The applied review checklist scales to handle various scenarios, from minor modifications to massive rewrites, systematically identifying security vulnerabilities and quality gaps across different change sizes.