A release command that sends the current branch through the project's checks, creates and tracks a pull request, and merges it when validation succeeds. A pull request is a proposed code change for review before it enters the main branch.

Use `shipyard pr` to ship a branch to `main`. It also checks skill updates, applies required version bumps, and reports a clean failure if the process cannot complete.

It coordinates checks, version updates, pushing, review tracking, validation, and merging in one prescribed workflow.

pr — Command for Claude Code by Generous-Corp: A release command that sends the current branch through…

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 commands/generous-corp/pulp/pr

Clone the repo

git clone --depth 1 https://github.com/Generous-Corp/pulp

Made for: Claude Code.

Or install pulp, the plugin that ships this one along with the rest of its 63 skills, 30 commands, 3 hooks, 1 MCP server.

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/commands/generous-corp/pulp/pr.svg)](https://agentmods.dev/commands/generous-corp/pulp/pr)

Your own site

<a href="https://agentmods.dev/commands/generous-corp/pulp/pr"><img src="https://agentmods.dev/badge/commands/generous-corp/pulp/pr.svg" alt="Measured on agentmods" height="20"></a>

Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 454 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00028	$0.00454
Opus 5	$0.00014	$0.00227
Sonnet 5	$0.00006	$0.00091
Haiku 4.5	$0.00003	$0.00045

Measured yesterday against content hash 83bfa4a6cf95, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

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

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/commands/pr.md · 40 lines

What it actually says

Run shipyard pr. It is the single orchestrator for shipping a branch to main:

Runs tools/scripts/skill_sync_check.py against origin/main. Hard-fails if a mapped skill path was touched without updating the corresponding SKILL.md (or a Skill-Update: skip skill=<name> reason="..." trailer).
Runs tools/scripts/version_bump_check.py --mode=apply, which bumps SDK (CMakeLists.txt), Claude plugin (.claude-plugin/plugin.json), and the marketplace entry (.claude-plugin/marketplace.json) as dictated by the heuristic + any Version-Bump: trailers on the branch.
Commits the bump as chore: bump <surfaces> if anything changed.
Pushes the branch, creates the PR, and records Shipyard tracking state.
Runs cross-platform validate + merge on green.
Returns only after the PR merges, or after a clean failure.

Do NOT run gh pr create and shipyard ship separately. Do NOT run the skill-sync or version-bump scripts by hand — shipyard pr invokes them in the right order with the right flags.

Direct gh pr create is an explicit emergency/manual bypass only. If used, tell the user the PR may not appear in Shipyard-managed state until it is reconciled or re-shipped through Shipyard.

pulp pr remains a compatibility wrapper that defaults to shipyard pr. Humans may configure pr.workflow=github or manual for their own checkout, but do not choose those paths unless the user explicitly asks for the bypass.

On completion, .github/workflows/auto-release.yml picks up the merged version bump on main and publishes a GitHub Release.

shipyard pr $ARGUMENTS

Use pulp status when you need to confirm the effective local PR workflow.

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.

yesterday First seen · 40 lines · 28 tokens per session scan A 83bfa4a6cf95

Subscribe to this mod's changes

pr is a command published in the GitHub repository Generous-Corp/pulp (16 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 454 once invoked, about $0.0001 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-09-04.

Git and workflow Releases

pr

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

push-and-release

land

release

release-notes

release

ship