/github-pr

Make it your own.

In Claude Code, use the slash command and add your context. In Codex, select github-pr from the just-vibe skill picker, then send the same brief.

Version 0.11.0 also supports /jv github-pr, /just-vibe github-pr and /jv:github-pr in Claude. See shortcut setup and context examples.

What the agent does

1. Resolve owner/repository, fork owner, head branch/SHA and intended base branch/SHA. Inspect the merge-base diff and existing matching PRs; distinguish local uncommitted work, local unpushed commits and the actual remote head.
2. Prepare the title/body from the candidate diff and relevant checks. Explain the trigger, changed behavior and verification limits. Follow the repository template without adding agent attribution, signatures or agent Co-authored-by text.
3. Create or update only when the exact remote action is authorized in the session; otherwise finish the concrete draft. Before a retry after timeout, query the exact head/base for an already-created PR so an uncertain response cannot create a duplicate.
4. Re-read the resulting PR identity and head/base. Checks for an older SHA do not establish readiness of the current head; if it changed during review, report that and validate the new candidate before claiming readiness.
5. Use the matching bundled evidence collector when available; read its result and limitations rather than treating exit zero as readiness. Revalidate identity before a dependent action.

Inputs

• Local change context for a draft; resolved repository and head/base for remote creation or updates. Issue links are optional unless the task requires them.

Optional context: scope, references, constraints, successCriteria, environment, mode, budget.

Scope

Reads

PR preparation or explicitly requested creation/update; no merge or unsolicited reviewer messaging.

Writes

Inspect/plan: inspect or propose; save requested artifacts only. Apply: make the requested changes or execute the requested operation within its resolved target and limits. Local preparation does not authorize live, remote, destructive or paid actions; existing explicit session authorization still applies.

Mode

Plan or draft locally when requested; apply when the user asks to create or update a PR in a resolved repository.

Prerequisites

Exact owner/repository and relevant issue/PR/ref; authenticated read access through an available connector or CLI for remote evidence. External writes require the requested operation, appropriate account permissions, and rechecking target state. Local preparation remains useful without write access.

Expected output

• Draft or verified PR URL, head/base identity, change summary, checks attached to their tested SHA and explicit readiness limits.

How the work is checked

• An existing matching PR is reused; a dirty local file absent from the pushed head is not described as part of the PR.
• Review newly prepared commit/PR/message text, including template or hook additions, for agent self-attribution before submission; verify the resulting artifact when available. Do not silently rewrite existing history or remove human credits.

When to stop or clarify

• Do not push unrelated commits or merge implicitly. Unknown creation results require deduplication before retry.

Handling missing context

Infer

Resolve owner/repository and PR/issue/ref from links, remotes and supplied artifacts; inspect available account and head identity.

Assume

Prepare local text or analyze supplied evidence if remote access is absent; label its freshness.

Ask

Ask only when repository/account/target ambiguity blocks the requested remote action; missing write access does not block local drafting.

Technical guidance

Evidence

Verify base/head repositories and SHAs, actual diff, template, related issues and check attempts.

Method

Describe final behavior and validation for the pushed head; inspect an existing matching PR before retrying creation.

Pitfall

A local green test can cover unstaged code absent from the PR; same branch names in forks identify different heads.

Check

Re-read remote head and rendered body after requested submission; include only demonstrated checks and user-owned attribution.

Situational decisions

When a PR already exists for the intended head/base: Reuse its identity and avoid duplicate creation; recheck head SHA before reporting readiness.

When the request is for local preparation or implementation: Draft the requested title/body from the local diff without requiring remote credentials; resolve repository and head/base identity before creating or updating the requested PR.

The coding agent follows this workflow using its available tools. Installation does not grant service access or guarantee an outcome. Read the compatibility notes.

Keep exploring