A coding-agent skill for preparing a pull request (PR), the change proposal developers send for review before merging code. It gathers branch and repository details and structures the PR around the product change.

Use it to create a PR from the current branch, link an issue such as AIS-810, choose another base branch, or create a draft PR.

It removes the repetitive work of checking the current branch, linking a Linear issue, choosing a base branch, and deciding whether the PR is a draft.

create-pr — Skill for Claude Code by mostafa-drz

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.

Any agent

npx skills add mostafa-drz/claude-skills --skill create-pr

Clone the repo

git clone --depth 1 https://github.com/mostafa-drz/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/skills/mostafa-drz/claude-skills/create-pr/github.svg)](https://agentmods.dev/skills/mostafa-drz/claude-skills/create-pr)

Your own site

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

Per session 4 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,614 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.00004	$0.01614
Opus 5	$0.00002	$0.00807
Sonnet 5	$0.00001	$0.00323
Haiku 4.5	$0.00000	$0.00161

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

code/create-pr/SKILL.md · 247 lines

How it starts

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

Create PR

Create a well-structured, product-focused pull request.

Preferences

Read ~/.claude/skills/create-pr/preferences.md using the Read tool. If not found, no preferences are set.

Context

On startup, use Bash to detect: current branch (git branch --show-current), upstream branch, commits ahead of upstream, and repo name (gh repo view --json nameWithOwner -q .nameWithOwner). Skip any that fail.

Command routing

Check $ARGUMENTS:

help → display help then stop
config → interactive setup then stop
reset → delete ~/.claude/skills/create-pr/preferences.md, confirm, stop
anything else (including empty) → create PR

Flags

Parse from $ARGUMENTS:

--base <branch> — override base branch
--draft — create as draft PR
--no-linear — skip Linear integration
Remaining text — treated as Linear issue ID if it matches pattern (e.g., AIS-810)

Help

PR — Create a well-structured pull request

Usage:
  /create-pr                         Create PR from current branch
  /create-pr <issue-id>              Create PR and link Linear issue
  /create-pr --base develop          Override base branch
  /create-pr --draft                 Create as draft
  /create-pr --no-linear             Skip Linear linking
  /create-pr config                  Set PR preferences
  /create-pr reset                   Clear preferences
  /create-pr help                    This help

Examples:
  /pr
  /create-pr AIS-810
  /create-pr --base develop --draft
  /create-pr AIS-810 --base main

What it does:
  1. Detects base branch (or uses preference/flag)
  2. Reads commits, diff, and Linear issue
  3. Builds product-focused PR description
  4. Pushes branch if needed
  5. Creates PR and links to Linear

Current preferences:
  (shown above under Preferences)

Config

Use AskUserQuestion:

Q1 — "Default base branch?" (auto-detect (default), main, develop, custom)

Auto-detect: checks tracking branch, falls back to repo default branch

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

9d ago First seen · 247 lines · 0 tokens per session scan A 8b1e3eddb19e

Subscribe to this mod's changes

create-pr is a skill published in the GitHub repository mostafa-drz/claude-skills (4 stars, last pushed 27d ago), licensed MIT. It adds 4 tokens to every session and 1,614 once invoked, about $0.0000 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.

Claude Code Code review Git and workflow ai-tools automation claude claude-skills developer-tools

visual-explainer-diff

Use when asked to visualize, explain, or document what changed between two git refs in a codebase. Triggers: 'show what changed in this PR', 'visualize the diff', 'explain the changes between main and this branch', 'generate a change report', 'what did this commit change architecturally', or any request to understand…

jircik/Visual-Explainer · 87 tokens

pr-review

Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.

oliver-kriska/claude-elixir-phoenix · 59 tokens

phx-pr-review

oliver-kriska/claude-elixir-phoenix · 61 tokens

resolve-pr-comments

Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments. Handles both change requests (fix or skip) and reviewer questions (explain using reasoning recalled from past Claude Code transcripts). Use when the user asks to "resolve PR comments", "fix review comments", "address PR…

tobihagemann/turbo · 95 tokens

fetch-pr-comments

Fetch and summarize review feedback and conversation from a GitHub PR (unresolved review threads, review bodies, and PR conversation comments) without making changes. Use when the user asks to "fetch PR comments", "show PR comments", "check PR for unresolved comments", "list review comments", "what comments are on the…

tobihagemann/turbo · 83 tokens

reply-to-pr-threads

Draft, confirm, and post replies to GitHub PR review threads. Handles per-category reply formatting, re-fetches thread resolution state so auto-resolved threads are skipped, and posts via GraphQL. Use when the user asks to "reply to PR threads", "post PR thread replies", or "draft PR reply messages".

tobihagemann/turbo · 71 tokens