create-pr

Create PR

Workflow

Run in the consumer repository and preserve the supplied arguments. Resolve --head to the current branch and --base to {TARGET_BRANCH} or main when they are omitted. Gather the branch, remote, existing PRs, recent commits, and diff statistics before composing the request.

Extract a ticket from the branch with {TICKET_PATTERN} (default [A-Z]+-\d+), then generate <type>: [<TICKET>] <summary> unless --title overrides it. Build the body from a concise summary, the ticket link when resolved, and verification evidence. Separate checks actually run from planned checks marked NOT RUN; for behavior changes, include a compact before/after example or evidence. Label an unobserved after-state as expected and list its check as NOT RUN. Add rollback and blast-radius details when they materially affect review. Use a visual aid only when it clarifies the change; do not include one by default. Before any PR creation, run the pre-flight checks in references/workflow.md, including git rev-list --count <base>..HEAD. A zero count stops with the exact message No commits between <base> and HEAD — nothing to open a PR for.

Dry-run is the default and only prints a copy-pasteable gh pr create command. --execute is the sole creation path: verify the branch is pushed, verify no PR already exists, require the existing GitHub authorization, ask for confirmation, and then report the URL. Do not push or create commits.

When NOT to Use

• The branch still needs commits or a push.
• An existing PR must be edited, merged, or closed.
• A release, tag, or deployment is the requested operation.

Output

• Dry-run: one copy-pasteable gh pr create command block and no PR URL claim.
• Execute: the URL returned by gh pr create.
• Missing refs, no commits, an unpushed branch, an existing PR, unavailable gh, failed authorization, or failed confirmation are terminal failures; never report a created PR without the URL evidence.