specdo-request-code-review

A formal code review gate enforces a complete active apply payload and diff scope before reviews begin, ensuring only valid, scoped changes proceed. It records a structured review_result gate event and routes to verification or receive-code-review based on outcomes.

To initiate a code review gate, provide a complete, resolved active apply payload from specdo-apply or a prior wrapper that includes changed_files and a diff_identity. The skill verifies this apply context and validates the diff scope to ensure full coverage of the review target.

Yes, a code review gate requires prior wrapper output, specifically a resolved active apply payload from specdo-apply or a similar wrapper. Without changed_files and a diff_identity to scope the review, the gate cannot enforce valid, scoped changes or preserve gate history.

After evaluating changed files, the code review gate records a review_result gate event and routes to either specdo-verification or specdo-receive-code-review. The routing decision depends on the review outcome and the presence of prior gate events in the history.

A code review gate fails to start without a diff identity because it enforces a complete active apply payload to scope the review target. The diff identity and changed_files are required to validate full coverage and preserve traceable, auditable governance of code changes.