create-pr

A command that prepares a pull request, which is a request to merge code into another branch, from the current feature branch into main.

In plain words
What is it for?
Use it to create a pull request for completed work, with a title, change summary, list of affected modules, and test plan.
Why use it?
It checks that the branch and commits are suitable, then gathers the change details and drafts the pull request text. This avoids manually checking the branch, reviewing the diff, and writing the summary.

Command for Claude Code

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/kayba-ai/agentic-context-engine/create-pr
Clone the repo
git clone --depth 1 https://github.com/kayba-ai/agentic-context-engine

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 532 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.00000 $0.00532
Opus 5 $0.00000 $0.00266
Sonnet 5 $0.00000 $0.00106
Haiku 4.5 $0.00000 $0.00053

Measured 2d ago against content hash 983d3299473d, 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 2d ago.

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 · 57 lines

What it actually says

Create a pull request for the current branch against main.

Arguments: $ARGUMENTS (optional) — base branch override (defaults to main)

Steps:

  1. Validate branch state:

    • Get current branch: git branch --show-current
    • If on main, abort with error: "You're on main. Switch to a feature branch first."
    • Determine base branch: use $ARGUMENTS if provided, otherwise main
  2. Check for unmerged commits:

    • Run git log <base>..HEAD --oneline
    • If no commits, abort: "No unmerged commits against . Nothing to PR."
  3. Gather context (run in parallel):

    • git diff <base>...HEAD --stat — file change summary
    • git log <base>..HEAD --format='%h %s' — commit list
    • git diff <base>...HEAD — full diff for understanding changes
  4. Draft PR title and body:

    • Analyze the commits and diff to understand the change
    • Write a short PR title (under 70 chars, imperative mood)
    • Write the body using this format:
      ## Summary
      <1-3 bullet points explaining the changes>
      
      ## Changes
      <bulleted list of key file/module changes>
      
      ## Test plan
      <how to verify the changes work>
      
  5. Present draft to user:

    • Show the proposed title and body
    • Ask: "Push and create this PR?" with options: Yes (create), Edit (let me revise), Cancel
  6. On approval:

    • Check if branch has upstream: git rev-parse --abbrev-ref @{upstream}
    • Push branch: git push -u origin HEAD
    • Create PR: gh pr create --title "<title>" --body "<body>" --base <base>
    • Show the resulting PR URL

On success, output:

✓ Pushed branch: <branch-name>
✓ Created PR: <pr-url>

Error handling:

  • If gh is not installed: "GitHub CLI (gh) is required. Install it: https://cli.github.com"
  • If not authenticated: "Run gh auth login first."
  • If PR already exists: show the existing PR URL with gh pr view --web
  • If push fails: show the git error and abort
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. 2d ago First seen · 57 lines · 0 tokens per session scan A 983d3299473d

Subscribe to this mod's changes

create-pr is a command published in the GitHub repository kayba-ai/agentic-context-engine (2,561 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 532 tokens. 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-30.