ship-pr

Opens a pull request for a ready branch, then reviews and addresses feedback to merge.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/Zeyad-37/tech-agency --skill ship-pr-zeyad-37
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship-pr
Source: https://github.com/Zeyad-37/tech-agency/tree/main/.claude/skills/ship-pr
Command: npx skills add https://github.com/Zeyad-37/tech-agency --skill ship-pr-zeyad-37

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When code is already implemented and committed on a branch but no pull request exists yet, getting it merged still requires opening the PR, requesting reviews, addressing feedback, and merging — a multi-step process this skill orchestrates as a single composition of two existing skills. ## Core Features & Use Cases - PR creation via /create-pr: Pushes the branch, captures UI screenshots, runs pre-push verification, creates the PR with the standard template, and requests a Copilot review. - Review and feedback loop via /review-and-address: Runs code review, waits for Copilot comments when available, applies fixes, and watches checks until green. - Optional auto-merge: The --auto-merge flag is forwarded so the PR merges automatically once all quality gates pass, with a trust boundary that disables it on untrusted feedback. - Use Case: You finished a feature branch with 5 commits and want it opened, reviewed, and merged without manually chaining commands — run /ship-pr and approve the single push gate. ## Quick Start Ask the assistant to ship the current branch as a PR by saying "ship this branch as a PR and review it to merge".

Frequently Asked Questions about ship-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I open a PR for an already-committed branch and get it merged?▼

Run /ship-pr on the branch. It invokes /create-pr to push and open the PR, then /review-and-address to review, address feedback, and merge once quality gates pass. You approve a single push gate at the start.

What is the difference between ship-pr, ship-it, and review-and-address?▼

ship-it covers kickoff and implementation plus the full PR flow, ship-pr handles a ready branch with no PR yet, and review-and-address closes out a PR that already exists. Choose based on how far along the work is.

Does ship-pr support automatic merging?▼

Yes, pass --auto-merge and it is forwarded to /review-and-address, which merges once all quality gates pass. Auto-merge is disabled automatically if feedback includes untrusted input such as issue-level comments or possible injection text.

Can I target a branch other than the repo default with ship-pr?▼

Yes, pass --base <branch> and it is forwarded to /create-pr, which resolves and validates the target, including epic integration branches. The preflight guard then counts commits relative to that target.

What happens if a PR already exists for my branch?▼

The preflight check detects the existing PR via gh pr view and stops, directing you to run /review-and-address directly on that PR number instead of opening a duplicate.

Why does ship-pr stop with 'no commits ahead' error?▼

The guard counts commits with git rev-list origin/TARGET..HEAD and halts when the branch has nothing new relative to the target. Verify you are on the correct feature branch and that commits were actually made.