sync-docs-release

# 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 — every edit, commit, and release action stays visible in this session. ## 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). Summarize the doc edits for the user before proceeding. ## Step 2 — Land the doc changes sync-docs leaves its edits uncommitted in the current checkout. **Never commit them to the repository's default branch**, and never treat a direct commit as acceptable merely because the checkout happens to be sitting on that branch. First, if `git status` shows no doc changes at all, report "no doc changes to commit" and go straight to Step 3. Otherwise pick the landing path: 1. Read the current branch (`git rev-parse --abbrev-ref HEAD`) and the default branch (`gh repo view --json defaultBranchRef -q .defaultBranchRef.name`). 2. Check the repo's `CLAUDE.md` / `AGENTS.md` for a branch, worktree, or pull-request policy. 3. Choose: - **Branch + PR** — the default. Required whenever the checkout is on the default branch or the repo mandates worktree/PR landing, and the right choice whenever the policy is unclear. - **Direct commit** — only when the checkout is already on a non-default working branch *and* no repo rule forbids committing there....