code-review-checklist

To review a pull request diff for security and code quality, apply a code review checklist that systematically evaluates correctness, vulnerability patterns like injection, maintainability practices, and testing completeness to catch defects before production.

A code review checklist for AI-assisted implementations should cover correctness, security, performance, and testing gaps, specifically checking for prompt-injection exposure and ensuring LLM outputs are sanitized before use in critical sinks.

Communicate code review findings consistently by using a severity-tagged lexicon with colored emojis like red for blockers, yellow for suggestions, green for nits, and a question mark for questions to ensure actionable and repeatable feedback.

Yes, this code review checklist supports developer workflows that require repeatable quality gates by enforcing validation of inputs and outputs, flagging common vulnerability patterns, and calling out anti-patterns with actionable feedback.

A code review should check for performance pitfalls like N+1 queries and common vulnerability patterns including XSS, CSRF, injection, and sensitive credential leaks to ensure code changes are safe and performant.

You need a structured code review checklist for refactoring code when you require repeatable quality gates to validate intended behavior, identify edge cases and failure modes, and ensure maintainability practices like DRY and SOLID are followed.