pr-ship
Skill3 starsChanged 13 days agoMITView on GitHub
Use when the user asks to ship, land, or merge a change or pull request ("ship it", "get this into main", "merge #42"). Opens the PR or marks a draft ready, babysits CI, keeps automated reviewers (CodeRabbit, Pullfrog, Claude, Copilot, ...) reviewing until a round comes back clean, then merges.
- Commits and pushes
3 other projects use a version of this.
Adopted by
Most recently taken up by
- huangxiaojian/claude-code-power-pack-litetheir own version, first seen Jul 30, 2026
- FerroxLabs/waylandtheir own version, first seen Jun 7, 2026
- AI-Answer/Agent-Clubtheir own version, first seen Mar 29, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- FerroxLabs/wayland★ 606same name
- AI-Answer/Agent-Club★ 9same name
- huangxiaojian/claude-code-power-pack-lite★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- comment-sweepSkill
- design-systemSkill
- domain-driven-designSkill
- feature-designSkill
- pr-babysitSkill
- resolve-merge-conflictsSkill
- test-driven-developmentSkill
- ux-brainstormSkill
- ux-stress-testSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Look up the PR the user named, or the current branch's: gh pr view --json number,url,state,isDraft,headRefName,baseRefName.
- Very specific: line 47
Use squash when the repo allows it, otherwise the method it does allow (merge commit over rebase if both): gh repo view --json …
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
PR ship
The user asked for the change to land: get it merged through every gate the repo has, once the automated reviewers have nothing new to say.
1. Get a PR that's ready for review
Look up the PR the user named, or the current branch's: gh pr view --json number,url,state,isDraft,headRefName,baseRefName. Work not yet on the remote (git status -sb) ships too: commit its files, asking if it's unclear which belong to it, and push them to the PR's branch.
- No PR. On the base branch, move the work to a new branch first. Push with
-u, thengh pr createagainst the default branch, ready for review. Fill in the repo's PR template if it has one (.github/pull_request_template.mdor.github/PULL_REQUEST_TEMPLATE/), and addCloses #<n>when the change resolves an issue. - Draft.
gh pr ready <n>. - Merged already. With newer commits on the branch, ship those as a new PR from the updated base; otherwise report it with the link and stop. Closed: ask before reopening.
2. Babysit it
Load the pr-babysit skill and run it to the end: it does the watching, fixing, replying, re-requesting, progress lines, and finishing. Shipping is the go-ahead it otherwise waits for: the PR leaves draft (step 1), and you merge it once step 4's gate holds, which ends the babysit. Steps 3 and 4 run inside that loop.
3. Review rounds
A round is one review of the current head from each automated reviewer on the repo. A round is clean when none of those reviews raises a new finding you change code for: a new thread, CHANGES_REQUESTED, or an actionable item in a review or summary body. A finding you answered without a code change, because the bot was wrong, keeps the round clean.
- Find the reviewers: bots that reviewed or commented on this PR or recent ones, and bots whose config or workflow is in the repo. references/review-bots.md has, per common bot, its trigger, whether it re-reviews each push on its own, and what clean looks like; for an unlisted bot, its earlier comments show the trigger.
- Get a review of the current head from each. Bots that review on open or push need nothing from you but a few minutes' wait; ask the others once per head with their trigger. If a bot hasn't answered 15 minutes after it should have, ask once more, then leave it out of the round and tell the user.
- Handle the findings as pr-babysit's Acting section says. When a bot answers your reply with nothing new (a thanks), resolve its thread; unlike a human, the bot never will:
gh api graphql -f query='mutation($id: ID!) { resolveReviewThread(input: {threadId: $id}) { thread { isResolved } } }' -f id=<thread id> - Repeat for the new head. Count the rounds whose findings you pushed fixes for. If the review after your third round of fixes still raises a new finding, stop: tell the user what is still being raised and that three rounds already ran, and ask whether to fix and continue, merge as is, or stop. Reviewers can produce new nits forever; the user decides when it's enough.
With no automated reviewer on the repo, the gate is CI plus the reviews the repo requires.
4. Merge
The ship request is the user's explicit, standing go-ahead to merge: once the gate below holds, run gh pr merge yourself in that same turn and report the result.
Merge when both hold for the same head:
pr_watch.py snapshotprintsREADY: yes. On a repo with no CI at all, set aside itsno checks reported yetblocker;- the latest round on that head is clean, with no bot review still pending on it.
Use squash when the repo allows it, otherwise the method it does allow (merge commit over rebase if both): gh repo view --json squashMergeAllowed,mergeCommitAllowed,rebaseMergeAllowed. Pin the merge to the head you checked, by its full SHA from gh pr view <n> --json headRefOid -q .headRefOid, so a push that lands in between stops it:
gh pr merge <n> --squash --match-head-commit <full head sha>If GitHub refuses, read why. For a merge queue or a pending requirement, add --auto and keep watching until it lands; auto-merge would also take a later push before its round ran, so gh pr merge <n> --disable-auto before pushing again and re-enable once the gate holds on the new head. For a required approval or check you can't satisfy, tell the user what's blocking and keep waiting. Merge through the repo's rules, never around them with --admin.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

