open-pr

open-pr

Wrap a feature branch and open a pull request. Single-shot workflow: rebase → lint → commit → push → PR.

You are operating autonomously once invoked. No confirmation prompts before push or PR creation. The only stop condition is a git conflict during rebase.

When NOT to run

Refuse and ask the user to clarify if any of these hold:

• The current branch IS the base branch (main, master) — there is nothing to PR.
• The repo has no GitHub remote (gh repo view fails) — a PR cannot be opened.
• The gh CLI is not authenticated (gh auth status fails) — authenticate first.
• The working tree has a destructive operation in progress (.git/MERGE_HEAD, .git/CHERRY_PICK_HEAD, an ongoing rebase) — finish or abort that first.

If none of those hold, proceed.

The workflow

Six phases. Do not skip. Track them so progress is visible to the user.

1. Preflight  — capture state, detect the base branch
2. Sync       — rebase onto origin/<base>; halt on conflict
3. Lint       — auto-detect and run the linter/formatter
4. Commit     — Conventional Commits message over the diff
5. Push       — force-with-lease (a rebase rewrites history)
6. PR         — gh pr create + share the URL

---

Phase 1 — Preflight

Run these, capture the output:

git rev-parse --abbrev-ref HEAD                       # current branch
git status --porcelain                                # dirty state
git rev-parse --git-dir                               # git dir (worktree-safe)
gh auth status                                        # gh ready?
git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null # default branch

Determine the base branch in this order:

1. git symbolic-ref refs/remotes/origin/HEAD → strip refs/remotes/origin/ → use it.
2. If that fails: git ls-remote --symref origin HEAD | awk '/^ref:/ {print $2}' → strip refs/heads/.
3. If still unknown: try main then master via git ls-remote --heads origin <name>.
4. If none resolve: refuse — the repo has no clear default.