create-pr

A command that updates a working branch from origin/main, prepares its commits, and creates a pull request on GitHub. A pull request is a proposal to merge changes into another branch.

In plain words
What is it for?
Use /create-pr to target main or another branch, create a draft with --draft, and prepare a GitHub pull request from a feature branch.
Why use it?
It organizes the branch history and pull-request description while checking conditions such as uncommitted changes and an existing pull request.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/magic3007/dotfiles/create-pr
Clone the repo
git clone --depth 1 https://github.com/magic3007/dotfiles
Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,632 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00040 $0.04632
Opus 5 $0.00020 $0.02316
Sonnet 5 $0.00008 $0.00926
Haiku 4.5 $0.00004 $0.00463

Measured yesterday against content hash 0a9bc9ab81f0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

create-pr scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

claude/commands/create-pr.md · 693 lines

How it starts

The opening of the file, as written. The whole thing — 693 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create Pull Request

Rebase from the latest origin/main, squash commits, and create a PR on GitHub with an intelligent title and description.

Usage

/create-pr [--draft] [--base <branch>]

Arguments:

  • --draft: Create as draft PR
  • --base <branch>: Target branch (default: main)

Workflow

Step 1: Verify Prerequisites

# Check current branch
git branch --show-current

# Check if on main/master (should NOT be)
if [[ $(git branch --show-current) == "main" || $(git branch --show-current) == "master" ]]; then
  echo "ERROR: Cannot create PR from main/master branch"
  exit 1
fi

# Check for uncommitted changes
git status --short

# Ensure gh CLI is available
gh --version

Action: If there are uncommitted changes, stop, and then ask user to commit or stash them first.

Step 2: Check for Existing PR

# Check if PR already exists for current branch
gh pr view --json number,title,url 2>/dev/null || echo "No existing PR"

Handle Existing PR:

  • If PR exists, inform user and ask permission to force-update it
  • Warn that this will rewrite the commit history and PR description
  • If user declines, abort the process

Step 3: Fetch and Rebase

# Fetch latest from origin
git fetch origin main

# Check divergence
git log --oneline HEAD ^origin/main

# Non-interactive rebase onto origin/main
git rebase origin/main

Handle Conflicts: If rebase fails due to conflicts, abort and let user handle rebase manually:

# On rebase failure, abort automatically
git rebase --abort

# Inform user to resolve conflicts manually
echo "Rebase failed due to conflicts. Please resolve manually and retry /create-pr"
exit 1

Step 4: Squash Commits into Single Commit

After successful rebase, squash all commits since origin/main into a single commit:

# Count commits to squash
git rev-list --count origin/main..HEAD

# Soft reset to origin/main (keeps changes staged)
git reset --soft origin/main

# Generate commit message using /gen-commit-msg logic
# See .claude/commands/gen-commit-msg.md for message generation rules

Read the full file on GitHub · 693 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 693 lines · 40 tokens per session scan A 0a9bc9ab81f0

Subscribe to this mod's changes

create-pr is a command published in the GitHub repository magic3007/dotfiles (10 stars, last pushed 6d ago), licensed MIT. It adds 40 tokens to every session and 4,632 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.