code-review-pre-merge-gate

To enforce a read-only review gate before pull request merges, invoke this skill during pre-merge checks. It coordinates with review lenses, validates base refs using shared scope detection, and returns a gate result with aggregated findings to ensure proper review discipline.

A pre-merge delivery gate is a read-only checkpoint that evaluates incoming pull request findings before allowing a merge. It dispatches read-only reviewer lenses, summarizes the findings, and outputs a delivery review outcome body for the owning workflow to act on.

Automate PR review checks by integrating this gate into your pre-merge workflow. It applies a read-only review process that dispatches reviewer lenses to evaluate pull requests, aggregating findings into a delivery outcome body that blocks unsafe merges.

Yes, the pre-merge gate supports both pull requests and merge requests. It applies the same read-only review discipline to PR and MR pre-merge checks in software repositories, coordinating with subagents to return a unified gate result and findings.

You need a read-only gate for merge decisions when your PR or MR review process has gaps that could allow unsafe or delayed merges. It enforces review discipline by validating base refs and evidence before returning a delivery review outcome.

The best way to summarize pull request findings for a delivery workflow is to use a read-only gate that dispatches and aggregates reviewer lenses. It evaluates the findings and produces a structured delivery review outcome body for the workflow to act on.