sync-docs-release

Runs three operations in strict sequence, all in the main session. Do not skip steps or reorder them, and do not delegate any step to a subagent.

Step 1 — Sync docs

Invoke the sync-docs skill via the Skill tool and follow it to completion here, passing the user's request plus any session context (target branch, last-sync SHA, specific files).

sync-docs works in its own worktree off the latest origin/<default> and ends with either "no doc changes" or an open docs PR. Summarize the doc edits and the PR for the user before proceeding.

Step 2 — Decide how the docs PR relates to the release

If sync-docs reported no doc changes, go straight to Step 3.

When the caller's approved plan already authorizes the docs-sync PR and its merge (as the milestone-workflow close-out does with merging on), take the merge-then-release choice below without asking. Otherwise ask the user once (AskUserQuestion) how Step 3 should relate to it:

• Merge the doc PR once its checks pass, then release from the updated default branch (recommend this one).
• Release now without the doc changes, leaving the PR open.
• Stop here with no release.

Treat their answer, or the caller's plan, as authorization for that one merge only. Their answer never authorizes the version-bump PR merge that create-release asks about. Never merge without that answer or that plan, and never merge past a failing or pending check.

Step 3 — Create a release

Skip this step entirely if the user chose "stop here".

If they chose merge-then-release, first wait for the PR's checks (gh pr checks <n> --watch); a failing or pending check stops the run with the PR left open and no release. Apply the create-release step 4 Merge bullet's rules to this docs PR: its no-checks rule (no checks reported counts as no failing check only when $DEFAULT requires no status check) and its merge-method choice (--squash, else --merge, else --rebase, as the repo allows). Then merge it with that method and its head pinned (--match-head-commit <head-sha>). After the merge command, read gh pr view <n> --json state,mergeCommit. When state is not MERGED (a merge queue holds the PR, or gh pr merge only enabled auto-merge), stop with the PR left open, report its state, and start no release. Otherwise git fetch origin and confirm git merge-base --is-ancestor <mergeCommit.oid> "origin/$DEFAULT" holds before create-release starts. On both release paths, remove the sync-docs worktree (git worktree remove <path>; the branch and the PR stay) and run git fetch origin before create-release starts. Do not check out or pull the local default branch.

Then invoke the create-release skill via the Skill tool and follow it to completion here, carrying the user's original context (target version or bump type, release-notes specifics) and how the doc changes landed (the PR number and merge commit, or the fact that they are still unmerged).

Report the tag and the release URL to the user.