A command for creating a GitHub pull request with an automatically prepared title and description. It examines the current branch, its commits, and the files changed against the base branch.

Use it to summarize changes, explain their purpose, list important updates, and note breaking changes or migration steps before opening the pull request.

It avoids writing a pull request from memory or leaving out context reviewers need. It also checks that the work is on a feature branch and whether a pull request already exists.

create-pr — Command for coding agents by infohata: A command for creating a GitHub pull request with…

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/infohata/mind-vault/create-pr

Clone the repo

git clone --depth 1 https://github.com/infohata/mind-vault

Or install mv, the plugin that ships this one along with the rest of its 23 skills, 6 commands, 8 agents, 2 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/infohata/mind-vault/create-pr.svg)](https://agentmods.dev/commands/infohata/mind-vault/create-pr)

Your own site

<a href="https://agentmods.dev/commands/infohata/mind-vault/create-pr"><img src="https://agentmods.dev/badge/commands/infohata/mind-vault/create-pr.svg" alt="Measured on agentmods" height="20"></a>

Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 393 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.

Model	Per session	Once invoked
Fable 5	$0.00012	$0.00393
Opus 5	$0.00006	$0.00197
Sonnet 5	$0.00002	$0.00079
Haiku 4.5	$0.00001	$0.00039

Measured 3d ago against content hash 4b15fa928f7b, 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 3d 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.

commands/create-pr.md · 52 lines

What it actually says

create-pr

Execute the create-pr command to generate and create a comprehensive GitHub pull request.

Steps to follow:

Check current branch and ensure it's not main:
- Run git branch --show-current
- Verify it's a feature branch
Check if PR already exists for this branch:
- Run gh pr view --json number or handle error if not exists
Determine base branch and analyze commits:
- Detect base: try gh pr view --json baseRefName -q .baseRefName if a PR exists; otherwise default to origin/main (or origin/deployment for release-branch projects)
- Run git log <base>..HEAD --oneline to see commits
- Run git diff <base>...HEAD --stat for file changes
Generate PR title:
- Should be clear, descriptive, and follow conventional format
- Based on the main changes in the branch
Generate comprehensive PR description:
- Include what changed and why
- List key changes or features
- Add context for reviewers
- Include any breaking changes or migration notes
- Write in the plain register — the PR body is read by a human reviewer, so use reading-speed sentences ("what changed / what it prevents"), never a compressed restatement of the diff (see skills/compound/references/mind-vault-promotion.md § Write for the two readers)
Create the PR:
- Use gh pr create --title "generated title" --body "generated description" --draft
- Make it draft initially for review
Provide the PR URL and summary

Requirements:

gh CLI configured
Branch should be pushed to remote
Should not be on main branch

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.

3d ago First seen · 52 lines · 12 tokens per session scan A 4b15fa928f7b

Subscribe to this mod's changes

create-pr is a command published in the GitHub repository infohata/mind-vault (2 stars, last pushed 6d ago), licensed Apache-2.0. It adds 12 tokens to every session and 393 once invoked, about $0.0001 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.

Git and workflow

create-pr

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

create-pr

What this file has done since we first saw it

Other commands, from other repositories

git

checklist

clarify

specify

analyze

converge