A command that commits your changes, pushes the branch to the shared Git repository, and creates or updates a pull request. A pull request is a request for teammates to review and merge your changes.

Use it when your work is ready for review, including checking the change history, writing a commit message, pushing the branch, and creating or updating its pull request.

It collects the usual review-and-submit steps in one guided process, so you do not have to remember each Git and GitHub command.

pr — Command for Claude Code by Smirnov-Labs

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/Smirnov-Labs/claude-skills

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

Your own site

<a href="https://agentmods.dev/commands/smirnov-labs/claude-skills/pr"><img src="https://agentmods.dev/badge/commands/smirnov-labs/claude-skills/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/smirnov-labs/claude-skills/pr"><img src="https://agentmods.dev/badge/commands/smirnov-labs/claude-skills/pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 669 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 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.00011	$0.00669
Opus 5	$0.00005	$0.00334
Sonnet 5	$0.00002	$0.00134
Haiku 4.5	$0.00001	$0.00067

Measured 11d ago against content hash c1085d75b4fd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, 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 11d 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/pr.md · 80 lines

How it starts

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

Pull Request Command

Follow these steps to commit changes, push to remote, and create or update a pull request:

Step 1: Review and Commit Changes

Run git status and git diff to review all changes
Analyze the changes and create a meaningful commit message that:
- Follows the repository's commit message style (check recent commits with git log)
- Clearly describes what was changed and why
- Is concise but informative
Stage all changes with git add .
Create the commit with the message ending with:

🤖 Generated with Claude Code

Co-Authored-By: Claude [email protected]

Step 2: Push to Remote

Check the current branch name with git branch --show-current
Push the branch to remote with git push -u origin HEAD (use -u to set upstream if needed)

Step 3: Check for Existing PR

Use gh pr view --json number,title,body to check if a PR already exists for this branch
If the command returns a PR, proceed to Step 4 (Update PR)
If no PR exists (command fails), proceed to Step 5 (Create PR)

Step 4: Update Existing PR

Read the current PR description using the command from Step 3
Analyze what new work has been added in the latest commits (use git log to see recent commits)
Create an updated PR description that:
- Preserves the original purpose and context
- Adds a new section or updates existing sections with the latest changes
- Clearly highlights what's new since the last update
Use gh pr edit --body "$(cat <<'EOF' [updated description here] EOF )" to update the PR description

Step 5: Create New PR

Analyze all commits on this branch (use git log main..HEAD or appropriate base branch)
Create a detailed PR with:
- A clear, descriptive title that summarizes the change
- A comprehensive body that includes:
  - Summary section: What was changed and why
  - Details section: Key changes made
  - Testing section: How to test or what was tested
  - Any relevant notes or context
Use `gh pr create --title "..." --body "$(cat <<'EOF'

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

11d ago First seen · 80 lines · 11 tokens per session scan A c1085d75b4fd

Subscribe to this mod's changes

pr is a command published in the GitHub repository Smirnov-Labs/claude-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 669 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

commit

A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.

echoVic/blade-code · 8 tokens

release-notes

Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.

OpenHands/extensions · 44 tokens

doctor

Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…

doncheli/don-cheli-sdd · 76 tokens

pr