create-pr

# Create Pull Request Draft a concise and descriptive title and a short paragraph for a PR. Explain the purpose of the changes, the problem they solve, and the general approach taken. When the changes involve clear runtime flows or state transitions, include Mermaid diagrams. ## Step 1: Analyze Changes If git is in a feature branch, examine all commit messages and the full diff to understand the overall changes. Analyze the diff for diagram opportunities (see Diagrams section below). ## Step 2: Run `/github-voice` Skill Run the `/github-voice` skill to load writing style rules. ## Step 3: Draft Title and Description Draft a title and description, embedding any diagrams in the body. Output the drafted title and description as chat text so the user can review it. ## Step 4: Confirm and Create Use `AskUserQuestion` for confirmation only. Generate a random tag so the body file is unique across sessions: ```bash head -c 4 /dev/urandom | xxd -p ``` Write the drafted body to `.turbo/pr/<tag>-body.md` (using the printed tag) with the Write tool, then create the PR with `gh pr create --body-file`: ```bash gh pr create --title "<TITLE>" --body-file .turbo/pr/<tag>-body.md ``` Do not set `--assignee` unless the user explicitly asks to assign someone. ## Diagrams GitHub renders Mermaid natively in PR descriptions via ` ```mermaid ` code blocks. Include diagrams only when they add clarity a text description can't — skip for trivial changes or obvious flows. ### Sequence Di...