pr

# /pr - Pull Request Creator The manual counterpart of build's Ship stage. Both write the body from the same rules. ## Input `$ARGUMENTS` is an Issue reference or context. If empty, generate from the current branch only. ## Phase 1: Preparation If there are no commits, the directory is not a git repository, or gh auth fails, report the error and abort. 1. Detect the base branch (§ Base Branch Detection) 2. Run the § Analysis Sources commands in parallel 3. Decide whether the change touches the UI (§ UI Change Detection). Phase 2 and Phase 3 both read this decision ## Phase 2: Generation 1. Choose the skeleton and write the body per ${CLAUDE_SKILL_DIR}/references/pr-writing.md. Fill Design Decisions per § Design Decisions Detection 2. When the change touches the UI and the repository's skeleton was taken, supply the two items § Pageshot Integration requires. The bundled skeleton carries both already, so nothing is needed there 3. Give it a title per § Title in ${CLAUDE_SKILL_DIR}/references/pr-writing.md 4. Refine the body inline against ${CLAUDE_SKILL_DIR}/references/prose-review.md ## Phase 3: Creation 1. If UI changes, invoke `use-workflow-pageshot` via Skill with the PR body (§ Pageshot Integration) 2. Push the current branch with `git push -u origin HEAD` 3. Write the body to a temp file and create the PR with `gh pr create --draft --title "<title>" --body-file <path>` (§ Creation Constraints). If a pageshot artifact exists, add the `--attach` from § Pageshot In...