prlisted

# /gku:pr — open or update the pull request for this branch The step between "the change is done" and "somebody reviews it". It reads the branch, writes a description a reviewer can actually use, and either opens the pull request or updates the one already attached to this branch. **The check that makes it worth running: does this branch read as one pull request?** A branch carrying a feature and an unrelated fix is two reviews pretending to be one, and it is where review quality goes to die. When that is what it finds, it says so and asks — it never decides for you, and it never rewrites your branch. It pushes commits you already made. It never commits for you, never merges, never force-pushes. ## Arguments - **nothing** — the current branch, against the profile's base branch. - **`<title>`** — use this as the pull request title instead of one written from the diff. - `--base <branch>` — target a different base. - `--draft` — open it as a draft. - `--dry-run` — print the coherence verdict, the title and the body. Create nothing, update nothing, push nothing. ## Step 1 — Preflight Read `.claude/repo-profile.json` (see `reference/repo-profile.md`; detect and cache it if missing) for the base branch. Stop early, with one line, on any of these: - **`gh` is missing or not authenticated** (`gh auth status`) — fall back to step 7's manual route rather than failing silently. - **On the base branch** — "You are on `<base>` — a pull request needs a branch." - **Detached H