git-remote-pr
Installation
SKILL.md
Git Remote PR

Open or maintain one GitHub pull request for the entire committed current branch. Use Git, gh, and GitHub APIs. Never use GitHub Copilot, gh copilot, browser automation, GitHub's generated PR description, or another model-backed GitHub service. The agent reading this skill writes concise reviewer-oriented prose from collected evidence; bundled scripts collect and verify facts only. Use PowerShell 7 (pwsh) on Windows, Linux, and macOS.
Routing and authorization
- Trigger on an explicit request to create, open, make, or refresh a GitHub PR, or
git remote pr./git-remote-prmay force selection where supported. Bareyoloorautonever triggers this skill. - The explicit PR request authorizes read-only preparation. In normal mode, show the preview below and stop for the exact
approve APR-...phrase displayed in that preview before any remote write. Approval for Preview A can execute only Plan A. yoloorautoattached to the same explicit PR request still requires the full preview, but it skips the approval requirement itself. Show the same preview as status, do not ask for or wait onapprove APR-..., and continue immediately with that just-presented plan's ID. Neither mode authorizes force push, rebase, reset, amend, merge, branch deletion, auto-merge, or unrelated writes.- A dirty worktree, including untracked files, blocks both modes. Explain that a PR contains committed changes only. Do not stage, commit, stash, discard, or automatically invoke
git-visual-commits. - A branch with no tracking configuration is a normal first-publication case: use the GitHub
originremote, or the sole GitHub remote when no GitHuboriginexists, and the exact current branch name. Prepare the full preview before publishing; execution uses a normalgit push --set-upstreamto publish and establish tracking.create yoloperforms that push and creates the PR without another approval reply. Ambiguous remotes, incomplete tracking configuration, and local/upstream branch-name mismatches block both modes; never silently retarget existing tracking after a rename. - Commit requests belong to
git-visual-commits; squash wording belongs togit-visual-squash-summary; release notes belong togit-remote-release; changelogs belong togit-keep-a-changelog. This skill independently reads the complete PR comparison.
Phase 1: prepare
- Check
gitandghare available. Run the read-only collector from the current working directory, with an absolute skill path. Use a unique operating-system temp directory, or ignored.bot/when needed. The collector fails closed for detachedHEAD, the base branch, dirty worktree, ambiguous publication remotes, incomplete or mismatched tracking, missing auth/assignee eligibility, empty comparison, diverged remote head, and ambiguous templates. It discovers the GitHub repository, authenticated account, actual default branch, fork parent when applicable, effective head branch, open PR, push need, and whether tracking must be established. Missing tracking does not require a preliminary push or configuration edit: compare localHEADagainst the fetched base, then preview publishing the exact current branch to the resolved remote. Valid same-name tracking may point to a branch not yet published or fetched. If existing tracking names a different branch, stop and explain the mismatch. Supply-Repository owner/repoor-Base branchonly when explicitly chosen or needed to resolve real ambiguity.