create-pr

A workflow for creating a GitHub pull request, which is a proposed set of code changes submitted for review.

In plain words
What is it for?
Use it when submitting work for review with the GitHub command-line tool, including staging relevant files and running Python checks when needed.
Why use it?
It handles the preparation work that can otherwise be easy to forget, such as checking GitHub access, committing changes, and pushing a branch.

Skill for Claude CodeCodex

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 skills/reflexioai/claude-smart/create-pr
Any agent
npx skills add ReflexioAI/claude-smart --skill create-pr
Clone the repo
git clone --depth 1 https://github.com/ReflexioAI/claude-smart

Made for: Claude Code, Codex.

Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,341 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00074 $0.01341
Opus 5 $0.00037 $0.00671
Sonnet 5 $0.00015 $0.00268
Haiku 4.5 $0.00007 $0.00134

Measured 3d ago against content hash afdd81ca687c, 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 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

<How the changes were verified — manual testing steps, automated tests run, curl commands, etc.>
Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • create-pr — 100% identical, 0 lines differ
.claude/commands/create-pr/SKILL.md · 140 lines

How it starts

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

PR Creator

Create well-structured, reviewer-friendly pull requests following best practices.

CRITICAL: This skill MUST always result in a PR being created. Do NOT stop early, do NOT ask the user to run another command first. Handle all prerequisites (committing, branching, pushing) inline and proceed to gh pr create.


Workflow

Step 1: Pre-flight Checks

Run these checks before anything else:

  1. Verify GitHub CLI authentication — run gh api user --jq '.login' to confirm the CLI is authenticated. If this fails, tell the user to run gh auth login first and stop.
  2. Determine the base branch — default to main. If the user specifies a different base, use that. Capture as $BASE_BRANCH.

Step 2: Commit Uncommitted Changes

Run git status to check for uncommitted changes. If there are uncommitted changes, commit them directly — do NOT delegate to another skill or tell the user to commit first.

  1. Stage changes — run git add <files> for relevant modified/untracked files. Do not stage .env or gitignored files.
  2. Lint and format — if Python files are staged, run:
    ruff check --fix <files> && ruff format <files>
    
    Re-stage any modified files.
  3. Commit — write a conventional commit message based on the staged diff:
    git commit -m "<type>: <description>"
    
    If precommit hooks modify files, re-stage with git add -u and retry (up to 3 times).

Step 3: Ensure Feature Branch

  1. Check current branch — run git branch --show-current.
  2. If on $BASE_BRANCH, create a feature branch:
    • Analyze the commits/changes to pick a descriptive name (e.g., feat/add-auth, fix/login-bug)
    • Run git checkout -b <branch-name>
  3. If on a different branch, check whether the branch has PR-worthy commits vs $BASE_BRANCH:
    • Run git log $BASE_BRANCH..HEAD --oneline
    • If there are commits, use the current branch as-is
    • If there are NO commits (branch is at same point as base), this means something went wrong — investigate and fix

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

  1. 3d ago First seen · 140 lines · 74 tokens per session scan A afdd81ca687c

Subscribe to this mod's changes

create-pr is a skill published in the GitHub repository ReflexioAI/claude-smart (772 stars, last pushed 4d ago), licensed Apache-2.0. It adds 74 tokens to every session and 1,341 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.