review

Perform a systematic code review by applying a standardized checklist across functionality, design, quality, and security to your pull request changes. It uses git diff analysis to evaluate modifications and markdown guidelines to structure actionable feedback.

Ensure code is ready for pre-commit verification by running through a pre-commit checklist that confirms all tests pass, code formatting is applied, and documentation is updated before you submit your changes.

Yes, you can review specific files or branches. The code review process supports targeting specific files or branches by leveraging git commands to isolate and analyze the exact code diff for your review.

Comment prefixes like BLOCKING, IMPORTANT, SUGGESTION, QUESTION, and NOTE improve code review feedback by categorizing the severity and intent of your comments. This standardization ensures clear, actionable feedback and faster feedback loops.

A checklist for quality assurance during a code review includes essential checks across functionality, design, quality, and security. It guides reviewers systematically through these defined areas using markdown guidelines to ensure code consistency.