requesting-code-review

To automate an independent code review, you dispatch a dedicated reviewer process for your feature branch that validates production readiness using whole-diff gates and execution evidence before merging. It grounds the assessment in approved plans and base/HEAD commits to enforce a strict, audit-ready review.

A gate review in a plan-routed workflow is a terminal whole-diff assessment that validates code changes against an approved plan and execution evidence. It enforces a structured reviewer process with checklists and artifacts to capture deviations and guide remediation before a production merge.

You ground a code review by providing the reviewer process with approved plans, execution evidence, and base/HEAD commits. This context anchors the assessment of production readiness, ensuring the review validates actual changes against the intended task boundaries.

Yes, the code review process captures deviations and tracks remediation through structured reviewer briefs and artifacts. It provides auditability by enforcing checklists and guiding the necessary fixes before allowing a merge.

Yes, this code review automation operates without external dependencies, functioning independently to dispatch dedicated reviews. It manages terminal whole-diff gates and task-boundary assessments entirely within its own structured process.

You need a dedicated code review for production readiness when merging code changes from a feature branch in a workflow-driven release. It is required to independently validate the diff, enforce strict checklists, and ensure remediation is complete before the final merge.