Bring the right reviewers into the work
A review keeps findings, discussion and status connected to the work being inspected. Requesting one is a step, not an approval.
A reviewable result and a briefing that says what changed and what the reviewer should inspect.
01 · Choose the target
Use the agent’s Review action or brief a reviewer persona on the relevant changes, document or artifact.
02 · Use owners for project-file review
The project’s .agents/owners.json map selects reviewer personas for changed file paths. Keep ownership rules aligned with the project.
03 · Work through findings
Reply with a fix or a reasoned explanation. The reviewer checks the response and resolves or dismisses the finding.
04 · Make the final decision
Check the result and any remaining findings. A review does not automatically authorize merging or publishing.
A concrete record of what was questioned, what changed and what still needs a decision.
Need more detail? Open the in-app Docs or browse source and contributor references ↗.