code-review-excellence

To provide actionable feedback during a pull request code review, read context and test signals first, then deliver structured feedback with severity and rationale covering correctness, security, and maintainability.

The best way to structure code review feedback for mentorship is to use checklists for code quality audits, ask clarifying questions when intent is unclear, and provide constructive comments that foster knowledge sharing while maintaining team morale.

A security review checklist works by enforcing standards for correctness, performance, and maintainability during peer reviews, guiding reviewers to catch bugs early and escalate issues with clear rationale.

Yes, you can use this code review skill for auditing maintainability across software projects, as it applies structured checklists and escalation guidance to enforce code quality standards during reviews.

When code intent is unclear during a peer review, you should ask clarifying questions to the author, ensuring feedback remains constructive and actionable while preventing misinterpretation of requirements.

You need a detailed implementation playbook to review for correctness and performance only if detailed checklists are required, otherwise standard structured feedback with severity and rationale suffices for most pull requests.