A command that creates or updates a GitHub pull request for the current branch. A pull request is a request to review and merge code changes into a shared repository.

Use it to open a new pull request or update the existing one for the branch you are working on.

It handles the repeated checks around the current branch, existing pull requests, authentication, and writing a description that non-developers can understand.

pr — Command for Claude Code by BitYoungjae: A command that creates or updates a GitHub pull…

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/bityoungjae/marketplace/pr

Clone the repo

git clone --depth 1 https://github.com/BitYoungjae/marketplace

Made for: Claude Code.

Or install gitkkal, the plugin that ships this one along with the rest of its 3 commands.

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/bityoungjae/marketplace/pr.svg)](https://agentmods.dev/commands/bityoungjae/marketplace/pr)

Your own site

<a href="https://agentmods.dev/commands/bityoungjae/marketplace/pr"><img src="https://agentmods.dev/badge/commands/bityoungjae/marketplace/pr.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 2,740 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.1	$0.00014	$0.02740
Opus 5	$0.00007	$0.01370
Sonnet 5	$0.00003	$0.00548
Haiku 4.5	$0.00001	$0.00274

Measured 6d ago against content hash 8183bee45671, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 6d 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.

plugins/gitkkal/commands/pr.md · 331 lines

How it starts

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

gitkkal pr

Creates or updates a Pull Request. Auto-detects existing PR for current branch.

The PR body must be readable by non-developers (product managers, designers, business stakeholders). Anyone should be able to grasp the purpose and impact of the change without opening the diff.

Critical Rules

NEVER include Co-Authored-By lines in PR body
NEVER use git push --force
NEVER modify already merged PRs
NEVER create PR from main/master branch
ALWAYS use HEREDOC for PR body

Usage

/gitkkal:pr                              # Create or update (auto-detected)
/gitkkal:pr emphasize refactoring        # With hint

Prerequisites

1. Load Configuration

git rev-parse --show-toplevel  # Find project root

Read {project_root}/.gitkkal/config.json. If not exists, use defaults and display once: "Using default settings. Run /gitkkal:init to customize."

2. Verify GitHub CLI

gh auth status

If not installed: "GitHub CLI is required. Install from https://cli.github.com" If not authenticated: "Run gh auth login to authenticate."

Mode Detection

gh pr view --json number,state 2>/dev/null

Succeeds + state is OPEN → Update Mode
Fails or state is CLOSED/MERGED → Creation Mode

PR Creation Mode

1. Check Branch Status

git branch --show-current
git remote show origin | grep 'HEAD branch'
git status -sb
git log origin/$(git branch --show-current)..HEAD --oneline 2>/dev/null || echo "no-remote"

If on main/master → Error: "Cannot create PR from main branch. Create a new branch first."

2. Gather Change Information

Run in parallel:

git log main..HEAD --oneline      # Commit history with messages
git diff main...HEAD --stat       # File-level change summary

IMPORTANT: Analyze ALL commits from base branch, not just the latest.

3. Understand Semantic Intent

Use staged analysis to avoid reading unnecessarily large diffs.

Step 1: Analyze commit messages + --stat first. Most PRs have descriptive commit messages that reveal intent; --stat shows scope.

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

6d ago First seen · 331 lines · 14 tokens per session scan A 8183bee45671

Subscribe to this mod's changes

pr is a command published in the GitHub repository BitYoungjae/marketplace (6 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 2,740 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.

Code review Git and workflow

pr