pr-automerge

Automating GitHub PR merge workflows safely requires enforcing policy-driven gates like NO FINDINGS checks and base-branch constraints. This Skill automates Stage 3 reviews, findings remediation, and ICC-REVIEW receipt validation to ensure all criteria are satisfied before merging.

An ICC-REVIEW receipt in PR automation is a validation record confirming that a Stage 3 review found no issues. This Skill checks the ICC-REVIEW receipt to enforce a NO FINDINGS gate, ensuring no unresolved review findings remain before allowing a merge.

Yes, you can enforce a no findings check before auto-merging a PR. This Skill applies gating logic that verifies the ICC-REVIEW receipt shows NO FINDINGS, alongside base-branch constraints and post-review approvals, to determine if an automated merge is safe.

To start a Stage 3 review for a specific GitHub PR, you initiate the workflow by specifying the PR number. This triggers a dedicated reviewer subagent to identify findings, validate the ICC-REVIEW receipt, and manage the automated merge process.

Automated PR merging does support base-branch constraints. This Skill enforces gating logic that includes checking base-branch constraints, optional auto_merge behavior, and post-review approvals to ensure merges only occur under strictly defined conditions.

You should avoid using automated PR merge tools when your workflow requires manual intervention for findings remediation or lacks strict policy enforcement. Without automated Stage 3 reviews and ICC-REVIEW receipt validation, auto-merging may bypass necessary safety gates.