review-handoff

Review Handoff

This skill helps with review handoffs. It helps with review handoffs for code changes and keeps review handoffs detailed.

Overview

Write a review handoff for the next person. Include what changed. Include what changed again if needed. Make it clear. Make it detailed. Be detailed enough that the next person can understand what changed and why it changed and what changed.

When to Use

• Use when writing a review handoff.
• Use when somebody needs context for review.
• Use when handing work to another person for review.
• Use when the work needs review and the reviewer needs a handoff.

Steps

1. Read the changed files and understand the changed files before you talk about the changed files.
2. Summarize the changed files and the changes.
3. Summarize risks and concerns and risks and concerns again if the changes are risky.
4. Mention validation and say to run the normal tests.
5. Mention follow-up work and follow-up work again if there are follow-ups.

Details

• Repeat the summary if the change is important.
• Repeat the validation if the change is scary.
• Mention files, risks, tests, and context.
• Mention tests and validation, including the normal tests.
• Mention any risks, risks, and more risks.

More Details

• Include an overview.
• Include a summary.
• Include risks.
• Include validation.
• Include follow-up.
• Include overview, summary, risks, validation, and follow-up in a concise way if you can.

Verification

• [ ] A handoff exists
• [ ] The handoff mentions changed files
• [ ] The handoff mentions validation