merge-pr

Safe pull-request merging is automated by reading the Claude workflow as the source of truth and executing it in the Codex environment. This validates safety checks, approvals, and conflict resolution before applying a policy-compliant merge.

Yes, approval validation and conflict resolution are enforced before execution. The workflow reads Claude's source configuration and only proceeds with the merge after verifying that all required automated checks and governance approvals successfully pass.

Adapting a Claude PR merge workflow for Codex involves reading the SKILL.md source file and automatically executing its defined steps in the Codex environment. This ensures consistent application of merge strategies across multiple repositories.

Yes, the Claude SKILL.md file is required as the canonical source of truth. The workflow reads this file to understand the necessary merge policies, safety checks, and approval requirements before executing any pull-request merge operations.

Automated pull-request merges fail governance requirements when safety checks, approvals, or conflict resolution steps are incomplete. The workflow enforces policy compliance by validating these conditions against the Claude source file before allowing execution.

An auditable trail for pull-request merges is needed when executing critical updates across repositories. This workflow generates an auditable trail by validating automated checks and governance requirements before applying the merge strategy.