requesting-code-review

name	requesting-code-review
description	Use when: prepare completed work for review so a reviewer can evaluate it quickly.

Goal: hand over a change that is easy to review and verify.

Use for:

• opening a pull request or asking for human/agent review
• packaging a branch so intent and evidence are clear
• self-reviewing before involving others

Workflow:

1. Self-review the full diff as if you did not write it.
2. Confirm tests exist and pass; capture the evidence.
3. Remove debug code, dead paths, and unrelated churn.
4. Write what changed, why, and how it was verified.
5. Call out risks, trade-offs, and areas needing scrutiny.
6. Keep the change focused; split unrelated work.

Review description:

• problem and chosen approach
• summary of changes by area
• test evidence and how to reproduce
• known risks and open questions

Rules:

• never request review without running the tests first
• keep diffs small and single-purpose
• flag your own uncertainty instead of hiding it
• do not bundle refactors with behavior changes