requesting-code-review

Prepare a code review package by documenting pre-flight checks, self-review findings, a concise change summary, and test evidence in a structured PR description to streamline feedback. This minimizes back-and-forth by ensuring all materials are complete and organized before submission.

A self-review checklist should validate that tests pass, code is formatted, no obvious issues remain, and should document findings alongside test evidence and a change summary. This ensures the PR is ready for review and satisfies automated check requirements.

Generate a concise change description that captures the modifications made during the feature PR or bug fix, then attach test results to support the review. Structuring this with clear focus areas guides reviewers effectively through the code changes.

Pre-flight checks apply across feature PRs, bug fixes, refactors, and any change involving security-sensitive code. They validate tests, formatting, and issue resolution before submitting a PR, ensuring consistent readiness regardless of the change type.

Structure the PR description by assembling pre-flight checklist results, self-review findings, change summaries, test evidence, and specific review focus areas. This structured approach guides reviewers through security-sensitive code changes efficiently.

Test evidence in a code review request supports the review process by proving automated checks passed and validating the changes. Attaching test results alongside the change summary reduces reviewer uncertainty and minimizes review iteration cycles.