/create-pr

Use when the user asks to open, create, update, or revise a pull request.

Scope (do not drift)

• Subject = committed changes on the current branch vs the remote default base (git log <base>..HEAD, git diff <base>...HEAD).
• Dirty / untracked / open-editor files that are not in that diff are out of scope — ignore them; do not start branding, a11y, or polish work.
• Do not invent todos or explore→edit loops. This skill is ship-the-branch, not implement-a-feature.
• If unrelated dirt exists, open the PR from commits anyway and mention dirt in one line after.

Tool

Call pr_manage — do not shell gh pr create / gh pr edit when this tool is available.

create_pr

pr_manage({
  action: "create_pr",
  title,
  body,
  base_branch?,  // default: repo default
  draft?,        // true only if they asked for a draft
  branch_name?,  // default: current branch
  add_labels?,
})

Write title/body from git log / git diff against the base. Keep the body concise (summary + test plan). Ready for review unless they said draft.

If the result is needs_confirmation (PR already exists on the branch), call update_pr with the discovered URL/number — do not open a duplicate.

update_pr

pr_manage({
  action: "update_pr",
  pr_url?,       // optional when current-branch PR exists
  title?,
  body?,
  base_branch?,
  add_labels?,
  remove_labels?,
})

Pass at least one field to change.

Auth

On auth errors, tell the user to run gh auth login -h github.com. No A/B/C menus.

After success

Keep the chat reply to one line with the PR URL. The feed shows an Open PR card.