pr

# Open a pull request Work the steps in order. A pair of hooks runs alongside them and refuses the shortcuts. A direct `gh pr create` is out, so is a `gh pr edit` rewriting the title or body, and so is any publish whose description the reviewer hasn't seen in its current form. This skill ends when the pull request is open. From there `watch-pr`, `fix-pr`, and `merge-pr` take over, and step 8 routes to whichever the operator asked for. ## Preflight !`bash ${CLAUDE_SKILL_DIR}/scripts/preflight.sh` ## Step 0: open the task list Create these with `TaskCreate`, then move each through `in_progress` and `completed`. 1. Confirm the branch is ready 2. Draft the description in PR_AGENTDESC.md 3. Clear the prose gates with fix-prose 4. Review the draft with review-pr-description 5. Run the validator and the prose gates 6. Ask the operator how far to take it 7. Publish the pull request 8. Route the rest Stop before any of it where preflight reports a rebase, merge, or cherry-pick in progress, or a missing precondition. Say what's wrong and hand back. ## Step 1: confirm the branch is ready Preflight answered each of these, so read rather than re-run: - The branch has commits the base doesn't. Nothing to open otherwise. - The branch isn't the default branch. - Uncommitted changes stay out of the pull request. Where preflight listed some, say so and let the operator decide before going on. - A pull request may already exist. Where one is open, publishing updates it rather than op...