Inspect branch, status, remotes, and authentication:

git branch --show-current
git status --short
git remote -v
gh auth status

If there is no current branch, stop and explain that the repository is in detached HEAD.
Determine the target branch:
- Use the user-provided base branch when present.
- Otherwise infer from common local/remote bases such as main, master, or develop.
- If multiple bases are plausible, ask which base to use.

Gather context:

git log --oneline <base>..HEAD
git diff --stat <base>...HEAD
git diff <base>...HEAD
gh pr list --state all --head <current-branch>

If a PR already exists for the branch, stop and return its URL unless the user explicitly asked to update or recreate it.
Generate:
- Title under 72 characters in Conventional Commit style when appropriate.
- Markdown body with ## Summary, ## Testing, and ## Breaking Changes only when relevant.
- Concise, factual bullets based on commits and diff.
If the branch has no upstream or is not available on the remote, push it:
```
git push -u origin HEAD
```
If multiple remotes are plausible and origin is not clearly correct, ask which remote to use.

Create the PR:

gh pr create --base <base> --head <current-branch> --title "<title>" --body-file <body-file>

Content Rules

Mention tests that were actually run. If none were run, write Not run.
Include breaking changes only when the diff or commits support them.
Reference related PRs or issues only when visible in branch names, commits, or user input.
Skip internal implementation detail unless it helps reviewers understand risk.

Guardrails