/pr

Make it your own.

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

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

What the agent does

1. Inspect the final diff, separate unrelated edits and account for generated artifacts.
2. Describe user-visible behavior before implementation details, and include only checks supported by verified evidence.
3. All changes are owned by the user. Add no agent/model self-attribution, AI-generated signature, badge, or agent Co-authored-by trailer to commits, PRs, comments, release notes or messages. Use the existing user Git identity; preserve legitimate human attribution and required third-party notices.

Inputs

• branch/base, intended change, and available verification results.

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

Scope

Reads

Prepare a PR title/body and diff summary; submission is handled by `github-pr` when requested.

Writes

No source changes in inspect/plan. Save only requested planning artifacts. A separately requested repair uses the relevant implementation workflow.

Mode

Plan; branch/base, intended change, and available verification results.

Prerequisites

Resolve the user brief and inspect the relevant project or supplied evidence. External capabilities are optional unless the selected action actually needs them.

Expected output

• Reviewable title and problem/behavior description with validation, risk notes and readiness gaps.

How the work is checked

• Description matches the final diff; unrun tests are not listed as passing.
• 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

• Flag unresolved conflicts, missing base, or unintended files. Do not push, open a PR, or message reviewers from a preparation-only request.

Handling missing context

Infer

Resolve the named files, existing scripts, current task and earlier corrections from the conversation and repository.

Assume

Use the narrowest interpretation that completes a reversible local task; state a consequential assumption once.

Ask

Ask when competing targets or incompatible success conditions would change the result; continue independent inspection first.

Technical guidance

Evidence

Inspect the intended diff, acceptance criteria, actual verification and repository template.

Method

Draft a self-contained title/body around final behavior, scope and evidence; preserve user ownership.

Pitfall

Local PR drafting does not authorize pushing or posting, and unrun checks cannot appear as passed.

Check

Reconcile every claim with the final diff and actual check identity, including any material limitation.

Situational decisions

When local changes are absent from the pushed head: Identify them as pending and do not describe them as submitted.

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