request-review

To send peer review requests with context, you dispatch review requests to cross-family reviewers by matching their family and role, attaching gate reports, discussion paths, and a five-line excerpt for intent assessment.

When automating a cross-family review request, you need to attach a gate report, a path to original discussions, and a concise five-line excerpt to provide reviewers with complete context and supporting evidence.

No, this review request workflow requires a gate report generated after your self-check passes, ensuring that peer review is only scoped to situations where additional eyes are needed for thorough quality verification.

The review-target-id is a generated traceable identifier attached to your archived review request, allowing reviewers to reference the centralized mailbox record and create an isolated sandbox environment for assessment.

The best way to archive peer review collaboration requests is to send them to a centralized review mailbox, attaching the gate report and discussion paths to maintain a traceable record of the cross-family review dispatch.

Your automated review request requires a five-line discussion excerpt to help cross-family peer reviewers quickly assess the original intent and scope of the work before evaluating the attached quality gate reports.