A command that prepares the information for a GitHub pull request, which is a proposed set of code changes for review and merging. It examines the current branch, commits, differences, changed files, and available base branch.

Use it to generate a pull-request title, summary, change list, changed-file descriptions, and testing section from the current Git history and diff.

It turns repository changes into a consistent summary, making the proposal easier for reviewers to understand and check.

pr — Command for Claude Code by hackermanishackerman

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.

Clone the repo

git clone --depth 1 https://github.com/hackermanishackerman/claude-skills-vault

Made for: Claude Code.

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/hackermanishackerman/claude-skills-vault/create-pr/github.svg)](https://agentmods.dev/commands/hackermanishackerman/claude-skills-vault/create-pr)

Your own site

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

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/hackermanishackerman/claude-skills-vault/create-pr"><img src="https://agentmods.dev/badge/commands/hackermanishackerman/claude-skills-vault/create-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 721 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod 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.1	$0.00010	$0.00721
Opus 5.5	$0.00004	$0.00288
Sonnet 5.5	$0.00002	$0.00144
Haiku 4.5	$0.00001	$0.00072

Measured 1mo ago against content hash 75f30c6f1631, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 1mo 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.

Origin

This is a copy

100% identical to pr — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

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

How it starts

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

Pull Request Workflow

Execute this workflow to prepare a GitHub Pull Request:

1. Gather Branch Information

Run git branch --show-current to get current branch name
Run git config user.name and git config user.email
Show: "📍 Current branch: [branch_name]"
Show: "👤 Author: [name] <[email]>"

2. Determine Base Branch

Check if main or master exists as the default branch
Use the appropriate base branch for comparison

3. Analyze Changes

Run git rev-list --count [base]..HEAD to count commits
Run git log [base]..HEAD --oneline to list all commits
Run git diff [base]..HEAD --stat to show changed files summary
Run git diff [base]..HEAD for detailed changes (summarize, don't show all)

4. Generate PR Details

Present the PR information in this format:

## PR Title
<type>: <concise description>

## PR Description

### 📋 Summary
<2-3 sentence overview of what this PR does>

### 🔄 Changes
- Change 1: description
- Change 2: description
- Change 3: description

### 📁 Files Changed
- `path/to/file1.ts` - description of changes
- `path/to/file2.tsx` - description of changes

### 🧪 Testing
- [ ] Unit tests added/updated
- [ ] Manual testing completed
- [ ] No breaking changes

### 📝 Notes
<Any additional context, screenshots needed, or deployment notes>

5. ASK FOR APPROVAL

Stop here and ask:

Ready to create PR?
1. Copy details to clipboard (manual PR)
2. Create PR via GitHub CLI (gh pr create)
3. Edit details first

WAIT for my response before proceeding.

6. If Option 2 (GitHub CLI)

Run:

gh pr create --title "<title>" --body "<body>" --base [base_branch]

Show the PR URL when complete.

PR Title Types

feat: New feature
fix: Bug fix
docs: Documentation changes
style: Code style/formatting
refactor: Code refactoring
test: Adding/updating tests
chore: Maintenance tasks
perf: Performance improvements
ci: CI/CD changes

Read the full file on GitHub · 103 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.

1mo ago First seen · 103 lines · 10 tokens per session scan A 75f30c6f1631

Subscribe to this mod's changes

pr is a command published in the GitHub repository hackermanishackerman/claude-skills-vault (2 stars, last pushed 6d ago), licensed MIT. It adds 10 tokens to every session and 721 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to pr, differing in 0 lines, and is treated as a copy.

Claude Code Code review Git and workflow ai automation bun claude claude-commands

review-prs

Parallel PR triage: decide merge-worthiness, prepare rebased worktrees, fix blockers, return them for human merge.

can1357/oh-my-pi · 0 tokens

settle-threads

The previous round read unresolved review threads on the pull request, and this round's implementer judged each one like a review finding: fixed it, declined it with evidence, or found it needs a person. Decide which threads are settled and write the reply each one gets. You write nothing yourself: the threads node…

coleam00/Archon · 0 tokens

pr