merge-pr

You can squash merge deterministically by applying gh pr merge --squash with --match-head-commit to validate the exact head commit before merging, ensuring workspace cleanup after success without pushing to main.

A deterministic squash merge uses --match-head-commit to guarantee the PR merges only if the head commit matches your reviewed state exactly. You need it when managing PRs that require exact head-commit matching and post-merge workspace cleanup.

You can inject co-author and reviewer metadata into the squash merge commit message during the gh pr merge --squash process using an automated skill that records the merge SHA and adds explicit trailers to preserve authorship.

Yes, you can automate PR workspace cleanup after a successful squash merge by using a skill that validates PR state and checks, performs the merge atomically, and then tidies the worktree automatically.

You should use --match-head-commit when merging a prepared PR to ensure the merge fails if the branch receives new commits after your review. This safety rail prevents merging unreviewed code and requires exact head-commit matching.

Limitations include not using the --auto flag and never pushing to main. The process requires the PR to be prepared and vetted beforehand, and it validates PR state and checks before performing the atomic squash merge.