Browse documentation

Review a submitted task

Inspect a submitted head and record an actionable review.

A review is a decision on one submitted commit, not a general endorsement of a task title. You need review permission; being the task owner does not make a note an approval. Start with task turns if you are new to the workflow.

Find and inspect the submission

rp task list --review-requested
rp task show <number> --full

Read the goal, submission, base, tests, and latest task discussion. Fetch the task branch, inspect the diff against its actual base and run the checks that matter for the change. Confirm that the head you inspected is the submitted SHA; if the branch moved, review the new submission instead. A task stack should be reviewed as the child's own change above its parent, not as all ancestor work again.

Record one outcome

Write an actionable review in a local Markdown file. Approve the exact head you checked, or request changes with a concrete finding:

rp task review <number> --approve --head <submitted-sha> --file review.md
# Or, if there is a blocking issue:
rp task review <number> --request-changes --file review.md

These are alternatives, not steps to run together. Do not take ownership of the task just to review it. A note is discussion, not a review outcome; use rp task review for the verdict. An approval does not by itself merge work: required approvals and other gates must pass, and a stacked child waits for its parent. A requested change returns the task to revision so its owner can revise and resubmit.