requesting-code-review

To prepare a code review package, assemble a defined review scope, change boundary tracking, and evidence of testing. This lets your reviewer assess changes quickly without missing requirements or verification context.

A thorough code review handoff includes scope definition, change boundary tracking with base and head SHAs, and verification evidence like tests or lint results. It clarifies what changed and what the reviewer should focus on.

Document verification evidence by recording tests, build results, lint checks, and manual checks. This evidence supports the review process and proves the changes work as intended before merging.

Yes, you can use a file-level diff summary for change boundary tracking when base and head SHAs are unavailable. Capturing the change boundary helps the reviewer understand the exact scope of the modifications.

You need a formal review package for major features, risky refactors, and pre-merge milestones. These scenarios require clear scope, boundaries, and verification context to ensure another reviewer can assess the change accurately.

Yes, a completed code-reviewer.md checklist is required for accurate assessment. It ensures the review package contains the necessary scope, boundary, and evidence details for a proper evaluation.