What is commit-push-pr?

A release workflow for Jujutsu, a version-control system, that turns local changes into commits, bookmarks, pushed branches, and pull requests. A pull request is a proposed change for review before merging.

Use it when you want to describe commits, create one bookmark per commit, push the stack to the remote repository, and open or update pull requests.

It combines the repeated steps needed to publish a stack of related changes and open review requests on GitHub.

commit-push-pr — Skill for Claude Code by jeffh/claude-plugins

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 jeffh/claude-plugins --skill commit-push-pr

Clone the repo

git clone --depth 1 https://github.com/jeffh/claude-plugins

Made for: Claude Code.

Or install jj, the plugin that ships this one along with the rest of its 3 skills, 2 commands.

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/jeffh/claude-plugins/commit-push-pr/github.svg)](https://agentmods.dev/skills/jeffh/claude-plugins/commit-push-pr)

Your own site

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

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

When invoked 804 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.00120	$0.00804
Opus 5.5	$0.00048	$0.00322
Sonnet 5.5	$0.00024	$0.00161
Haiku 4.5	$0.00012	$0.00080

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

Security

Grade A, and why

commit-push-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.

jj/skills/commit-push-pr/SKILL.md · 79 lines

How it starts

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

Commit, Push, and Create PRs

Execute the complete workflow from uncommitted changes to open pull requests:

Commit — Describe changes with proper commit messages
Bookmark — Create bookmarks for the stack
Push & PR — Push to origin and create/update pull requests

Context expectations

When invoked from /jj:commit-push-pr, the GitHub user login, remotes, working-copy status, stack log, open PRs, and any repo PR template are already in context. Do not re-fetch them. If invoked directly, gather them first:

gh api user -q '.login'
jj git remote list
jj status --no-pager
jj log --no-pager -r 'trunk()..@'
jj log -r 'trunk()..@' --no-graph -T 'separate(" | ", change_id.short(), if(description, description.first_line(), "(no description)"), bookmarks) ++ "\n"'
gh pr list --json number,title,headRefName,url,baseRefName --state open

From that context, identify: commits needing descriptions, existing bookmarks, existing PRs, and the GitHub username for the bookmark prefix.

Defaults (no prompting)

Bookmarks:

One bookmark per commit in the stack
Prefix <github-username>/; name derived from the commit description (lowercase, dash-separated)

PRs:

One PR per bookmark (stacked PRs)
Base each PR on its parent bookmark (or trunk for the first PR)
Published (not draft), pushed to origin

Steps

Execute without additional confirmation prompts.

Step 1: Commit — Invoke the jj:commit skill with the appropriate revset (skip if all commits have descriptions).

Step 2: Create Bookmarks (skip if commits already have bookmarks):

jj bookmark create <prefix><name> -r <change_id>
jj bookmark track <bookmark> --remote=origin

Step 3: Push and Create PRs (skip if no bookmarks need PRs):

jj git push
gh pr create --head <bookmark> --base <base> --title "<title>" --body "<body>"

Honor PR templates

If a PR template was found in context (e.g. .github/PULL_REQUEST_TEMPLATE.md), use its sections and checkboxes verbatim as the PR body, filling each section from the actual changes. When no template exists, write a concise body and do NOT include a "Test plan" section.

Read the full file on GitHub · 79 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 · 79 lines · 120 tokens per session scan A 36352503aa1f

Subscribe to this mod's changes

commit-push-pr is a skill published in the GitHub repository jeffh/claude-plugins (12 stars, last pushed 19d ago), licensed Apache-2.0. It adds 120 tokens to every session and 804 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-30.

Git and workflow Releases

release-announcement

Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.

paperclipai/paperclip · 42 tokens

release

Fully automate a release with version-bump and childhood.

thedotmack/claude-mem · 13 tokens

release-notes

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

phuryn/pm-skills · 57 tokens

commit-push-pr