Merge a pull request

Work the steps in order. A pair of hooks runs alongside them and refuses the shortcut: a direct gh pr merge, and any merge whose message the reviewer hasn't seen in its current form.

Left alone, GitHub writes the squash message by concatenating every commit on the branch. That text has never passed a commit-msg hook, and it arrives on the default branch where the rest of the toolchain assumes those hooks ran. Nothing lints it afterwards. This workflow writes the message itself and puts it through what a commit answers to.

Preflight

!bash ${CLAUDE_SKILL_DIR}/scripts/preflight.sh ${ARGUMENTS}

Step 0: the checklist

Track these steps with the session's task-list tools where it carries them. Newer harnesses leave those tools out by default, and a session without them works the list in order as written.