Review

Review changes against your standards and the original intent, and take feedback with rigour.

Refine review by task, stack and access

10 skills

Which part of code review do you need?

Review workflows serve different jobs. Before choosing a skill, decide whether you need findings on a patch, help preparing a review request, or a way to handle feedback already received.

  1. 01

    Reviewing a patch: provide the base and head revisions, the intended behavior and relevant callers. Ask for reproducible defects and missing requirements, with locations and evidence.

  2. 02

    Requesting a review: prepare the change summary, acceptance criteria and test results. This helps a reviewer inspect the change; it is not itself an independent review.

  3. 03

    Responding to feedback: verify each finding against the current code before changing it. Record what was fixed, what was rejected and why, then rerun affected checks.

Use the example review brief to scope a read-only review, or explore the review loop kit for the surrounding workflow.