open-pr

open-pr is a skill for Claude Code from dkmqflx/git-workflow-plugin. It costs 126 tokens per session (924 once invoked), scanned A, original, MIT.

A helper for opening a new pull request, which is a request to merge changes from one Git branch into another. It pushes the current branch, chooses the target branch, and prepares a title and description for your confirmation.

In plain words
What is it for?
Use it after committing changes to determine the base branch, verify the branch is suitable, push it, and create a pull request with an optional linked URL.
Why use it?
It removes the repetitive checks and writing involved in submitting completed changes for review. It also stops when the branch or working tree is not ready.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the git-workflow plugin — 5 skills shipped together

Good fit Use it after committing changes to determine the base branch, verify the branch is suitable, push it, and create a pull request with an optional linked URL.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dkmqflx/git-workflow-plugin/open-pr
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 dkmqflx/git-workflow-plugin --skill open-pr
Clone the repo
git clone --depth 1 https://github.com/dkmqflx/git-workflow-plugin

Made for: Claude Code.

Or install git-workflow, the plugin that ships this one along with the rest of its 5 skills.

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.

agentmods badge for open-pr

README.md
[![agentmods](https://agentmods.dev/badge/skills/dkmqflx/git-workflow-plugin/open-pr/github.svg)](https://agentmods.dev/skills/dkmqflx/git-workflow-plugin/open-pr)
Your own site
<a href="https://agentmods.dev/skills/dkmqflx/git-workflow-plugin/open-pr"><img src="https://agentmods.dev/badge/skills/dkmqflx/git-workflow-plugin/open-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.

agentmods 80×15 button for open-pr

Your own site · 80×15
<a href="https://agentmods.dev/skills/dkmqflx/git-workflow-plugin/open-pr"><img src="https://agentmods.dev/badge/skills/dkmqflx/git-workflow-plugin/open-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 126 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 924 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00126 $0.00924
Opus 5.5 $0.00050 $0.00370
Sonnet 5.5 $0.00025 $0.00185
Haiku 4.5 $0.00013 $0.00092

Measured 1mo ago against content hash 7a3f4e6c73a2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

open-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.

plugins/git-workflow/skills/open-pr/SKILL.md · 56 lines

How it starts

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

Open PR

Push the current branch and open a pull request via gh pr create.

Run this after committing your changes (see commit-each). Once the PR is merged, clean up with branch-done or worktree-done.

When to apply

Opening a new PR for the current branch. Do not apply to update, review, or comment on an existing PR.

Steps

  1. Determine the base branch:
    • If a dev branch exists locally or on the remote (git show-ref --verify --quiet refs/heads/dev or refs/remotes/origin/dev), the base is always dev. Stop here — do not fall through, whatever origin/HEAD points at.
    • Otherwise try git symbolic-ref refs/remotes/origin/HEAD and strip the refs/remotes/origin/ prefix.
    • If that fails, use the first of main, master that exists locally (git show-ref --verify --quiet refs/heads/<name>).
    • If none exist, stop and ask the user which branch is the base.
  2. Record the current branch: git rev-parse --abbrev-ref HEAD. If it equals the base branch, stop and notify the user — there's nothing to open a PR from.
  3. Check for uncommitted changes (git status --porcelain). If any exist, stop and tell the user to commit first.
  4. Check whether a PR already exists for this branch: gh pr view --json url 2>/dev/null. If one does, stop and report its URL instead of creating a duplicate.
  5. Push the branch: git push -u origin HEAD.
  6. Gather context for the PR description:
    git log <base branch>..HEAD --oneline
    git diff <base branch>...HEAD
    
  7. Draft a title (under 70 characters) and a body with a ## Summary (1–3 bullets) and ## Test plan (checklist) section, covering all commits on the branch — not just the latest.
  8. Collect any URLs the user passed with the invocation (/open-pr <link>, or a link written anywhere in the request). If there is at least one, append a ## Related section listing them as bullets at the end of the body. If there is none, leave the section out — never ask the user for a link.
  9. Show the drafted title and body to the user and get confirmation before creating.
  10. Create the PR:
gh pr create --base <base branch> --title "<title>" --body "$(cat <<'EOF'
<body>
EOF
)"
  1. Report the returned PR URL.

Read the full file on GitHub · 56 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. 1mo ago First seen · 56 lines · 126 tokens per session scan A 7a3f4e6c73a2

Subscribe to this mod's changes

open-pr is a skill published in the GitHub repository dkmqflx/git-workflow-plugin (1 stars, last pushed 2mo ago), licensed MIT. It adds 126 tokens to every session and 924 once invoked, about $0.0005 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-31.

Related

Other skills, from other repositories

procoder

Work like a senior developer in a repository governed by procoder: run the commit gate before calling anything done, format and lint through the binary, and drive the spec, plan, todo, backlog, and sprint chain in .procoder/. Use this skill when the repository contains a .procoder/ directory or an AGENTS.md naming…

azrtydxb/procoder · 101 tokens

dsh-plugin-publisher

A release tool for DSH plugins, where DSH is the DeepSeek Harness used to load these add-ons. It validates an existing plugin package, publishes it through npm, Git, or a tarball, and checks that the harness can load it.

lovstudio/skills · 82 tokens

lov-skill-optimizer

Audit and optimize one or more existing Agent Skills from a canonical source path, then bump semver, update README/SKILL.md/skill.yaml/CHANGELOG.md, and verify installed copies and catalog synchronization. Checks frontmatter, trigger quality, CLI hygiene, naming, portability, version drift, dirty worktrees, shared…

lovstudio/skills · 127 tokens

lov-rename-project

A project-renaming workflow that updates a product or repository name across source files, configuration, and documentation. It produces a reviewable plan and preserves compatibility-sensitive names and references where needed.

lovstudio/skills · 45 tokens

lov-gh-access

Open a private GitHub repo to external clients or contractors without making it public. Accepts a mixed list of GitHub usernames and/or email addresses, resolves each to a GitHub account (falling back to an email invitation when the user has no discoverable account yet), and invites them as collaborators with a chosen…

lovstudio/skills · 151 tokens

lov-skill-publisher

Publish or submit a validated Skill. Default to the LovStudio official website, run lov-skill-pricing automatically, and use other channels only when explicitly named.

lovstudio/skills · 38 tokens