A pull-request creation workflow for the current Git branch, including an automatically written description, issue links, roadmap updates, and metadata checks. A pull request is a proposal to merge branch changes into another branch.

Use it to create ready-for-review or draft pull requests, infer or override issue numbers, link multiple issues, and update the project roadmap.

It checks that the branch is suitable for review, connects the work to relevant issues, and turns the commit history into a consistent title and description.

create-pr — Skill for Claude Code by joshukraine/dotfiles

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 joshukraine/dotfiles --skill create-pr

Clone the repo

git clone --depth 1 https://github.com/joshukraine/dotfiles

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/joshukraine/dotfiles/create-pr/github.svg)](https://agentmods.dev/skills/joshukraine/dotfiles/create-pr)

Your own site

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

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

When invoked 1,227 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00025	$0.01227
Opus 5.5	$0.00010	$0.00491
Sonnet 5.5	$0.00005	$0.00245
Haiku 4.5	$0.00003	$0.00123

Measured 1mo ago against content hash 132307c3e281, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

claude/.claude/skills/create-pr/SKILL.md · 111 lines

How it starts

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

Create Pull Request

Create a pull request from the current branch with proper formatting and issue linking.

Command Options

All flags are optional. By default, the issue number is inferred from the branch name and the PR is created as ready-to-review.

--issue N: Override automatic issue linking with a specific issue number (or comma-separated list: --issue 123,175)
--skip-issue-link: Skip issue linking entirely
--draft: Create PR as draft

Your task

Verify prerequisites:
- Confirm current branch is not main/master
- Check that branch has commits ahead of base branch
- Ensure branch is pushed to remote (push if needed)
Generate PR title:
- Use branch name as fallback
- If single commit ahead: use commit message as title
- If multiple commits: create descriptive title based on branch name and commit themes
- Follow Conventional Commits format from global CLAUDE.md
Analyze commits for description:
- Get commit history: git log origin/<base-branch>..HEAD --oneline (use the base branch identified in step 1)
- Group commits by type (feat, fix, docs, etc.)
- Identify patterns and overall theme
Create comprehensive description:
- Summary section: 2-3 bullet points describing what this PR does
- Changes section: Categorized list of changes from commits
- Testing section: How the changes should be tested
- Notes section: Any implementation details or decisions
Update ROADMAP:
- Check if the work corresponds to a checkbox item in docs/prd/ROADMAP.md
- If a matching item exists, mark it complete ([x]) and commit the change to the branch before creating the PR
- If no matching item exists, skip this step
Identify and link related issues (discover → classify → confirm; don't rely on recall):
- If --skip-issue-link: skip this step entirely.
- Determine the primary issue(s) P:
  - --issue N (accepts a comma-separated list, e.g. --issue 123,175) → use directly as Close targets; skip discovery.
  - Otherwise extract from the branch name (fix/gh-123-... → P=123). If none can be determined, warn and ask whether to proceed with no linking.
- Discover candidates mechanically (do not depend on having read the issue earlier in the session):
  - Fetch the primary issue's body and comments: gh issue view P --json number,title,body,comments
  - Extract every #<number> reference from that output.
  - For each referenced issue M, get its state: gh issue view M --json number,title,state — drop anything already closed or that is a PR.
- Classify each open candidate by the language around the mention:
  - closes / fixes / resolves #M, or M is an unchecked task-list item this PR completes → Close (Closes #M)
  - part of / blocked by / relates to / see / parent #M → Reference (Refs #M, no closing keyword)
  - ambiguous → default to Reference and flag it
- Confirm before creating the PR:
  - Only the primary issue P, no other open candidates → proceed silently with Closes #P.
  - More than one candidate, or any ambiguous one → print a short table (issue · title · proposed Close/Ref) and ask for a one-line confirm/override first.
- Format: one keyword per line so GitHub parses them all — Closes #N per close target, Refs #N per reference.

Read the full file on GitHub · 111 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 · 111 lines · 25 tokens per session scan A 132307c3e281

Subscribe to this mod's changes

create-pr is a skill published in the GitHub repository joshukraine/dotfiles (429 stars, last pushed 5d ago), licensed MIT. It adds 25 tokens to every session and 1,227 once invoked, about $0.0001 per session on Opus 5.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-30.

Git and workflow Project management Ruby dotfiles macos rails vim zsh

mbo-plan

Plan a new objective end-to-end in this repo's docs/mbo Management-By-Objective system — turn a GitHub issue or a gss draft-PR worktree into consistent design/spec/plan artifacts and track it in docs/mbo/index.md. Use this whenever the user wants to START planning or designing a new feature, skill, CLI, or service…

sfc-gh-eraigosa/dotfiles · 260 tokens

issue-grooming

Use when the user wants to groom, triage, prioritize, or clean up the GitHub issue backlog of a repo: "groom the issues", "triage the backlog", "which issues are already done", "prioritize the open issues", "close stale issues", "label issues 1-5", "refactor old issues to match the repo", or a periodic backlog review…

sfc-gh-eraigosa/dotfiles · 140 tokens

show-issues-overview

Show a table-formatted overview of the current repository's issues, from GitHub Issues, GitLab Issues, or a TODO.md-like file when the project has neither. Use when the user asks what issues/tasks are open, wants to decide what to work on next, or invokes /show-issues-overview.

aiya000/dotfiles · 69 tokens

create-pr