Ship Now
The fast version of /ship. Local pnpm prep:urgent replaces the remote CI
wait and the 10-minute unchanged-head gate, then you admin-merge right away.
Everything else comes from ship: ownership, preflight, the ready PR, and
--match-head-commit. The explicit /ship-now request authorizes the merge
for your own PR. For anyone else's PR, ship's ownership rules apply.
Steps
Preflight as in ship. Find the PR:
gh pr list --head "$(git branch --show-current)" --state open --json number,url,author
Read every review summary and top-level inline comment (use
babysit-pr's two queries). Fix real issues, reply on each thread you
fixed or declined, and rerun the queries after every push, since a new bot
review is a new round.
Run the local gate:
pnpm prep:urgent
It uses --kill-others-on-fail, so a lane killed by a sibling's failure is
unknown, not green. Fix the failure and rerun only the narrow check for each
failed or unknown lane: that package's typecheck, the specific Vitest file,
the named guard, or pnpm exec oxfmt --check <files>. Rerun the full
command only when the fix crosses several lanes. When you report, say prep
recovered through targeted checks if it did. Don't say the whole command
passed when it didn't.
Push everything in one update. ship:push stages every publishable path,
so first check git status: if a dirty path isn't part of this task, stop
and leave it alone.
corepack pnpm ship:push -m "<subject naming the actual change>"
For an existing PR whose head isn't this branch on origin, push to the
verified head repo and ref as babysit-pr describes. Don't open a second
PR.
Merge immediately when the tree is clean and pushed, every review item is
fixed or answered with a reply that was actually posted, and the PR isn't
CONFLICTING. A reply you could only draft (someone else's PR, no comment
permission) blocks the merge. Re-read the live PR as in babysit-pr step 1
(open, base main, and either yours or a PR the user named for this merge) and its headRefOid. It must equal
git rev-parse HEAD, the head you validated and pushed. If it doesn't,
someone pushed: redo steps 2-4. When they match, write it as
ship_merge_head_oid and run:
gh pr merge <number> --squash --admin --match-head-commit <head-oid>
If the head moved, someone pushed. Redo steps 2-4 for the new head before
you merge it. Don't wait for remote CI or release checks.
Fetch origin/main and confirm the merge commit is in it, then rotate with
/new-branch's post-merge step.
After the merge
Because this path merged before remote CI finished, watch the workflows on
the merge commit:
gh pr checks <number> # PR CI keeps running on the merged head
gh run list --commit <mergeCommit.oid> --limit 50 --json name,status,conclusion,url
A failed query, or no runs listed yet, means unknown, not green. Keep checking until they finish.
Stop watching once the PR checks have all finished and the merge commit's
runs have finished, or successful queries have shown none for 10 minutes.
In that last case, report "no merge-commit runs seen", which is usually path
filters but unverified, rather than calling them green. Fix any failure on the fresh branch and send
it through /ship. If the PR body has a Reports section, run
/review-latest-feedback step 5 for those threads. Merging publishes beta
automatically. Beyond the merge commit's own workflows, beta, docs, and
release proof follow ship-and-monitor, when the user asks for it or a
concrete risk calls for it.
1---2name: ship-now3description: >-4 Fast-path the current branch to main: local `pnpm prep:urgent`, push, and an5 immediate admin merge without waiting for remote CI or the 10-minute gate.6 Use only when the user explicitly asks to merge immediately.7user-invocable: true8scope: dev9metadata:10 source: https://skillmd.com/skills/builderio/ship-now11 internal: true12---1314# Ship Now1516The fast version of `/ship`. Local `pnpm prep:urgent` replaces the remote CI17wait and the 10-minute unchanged-head gate, then you admin-merge right away.18Everything else comes from `ship`: ownership, preflight, the ready PR, and19`--match-head-commit`. The explicit `/ship-now` request authorizes the merge20for your own PR. For anyone else's PR, `ship`'s ownership rules apply.2122## Steps23241. Preflight as in `ship`. Find the PR:2526 ```bash27 gh pr list --head "$(git branch --show-current)" --state open --json number,url,author28 ```29302. Read every review summary and top-level inline comment (use31 `babysit-pr`'s two queries). Fix real issues, reply on each thread you32 fixed or declined, and rerun the queries after every push, since a new bot33 review is a new round.34353. Run the local gate:3637 ```bash38 pnpm prep:urgent39 ```4041 It uses `--kill-others-on-fail`, so a lane killed by a sibling's failure is42 unknown, not green. Fix the failure and rerun only the narrow check for each43 failed or unknown lane: that package's typecheck, the specific Vitest file,44 the named guard, or `pnpm exec oxfmt --check <files>`. Rerun the full45 command only when the fix crosses several lanes. When you report, say prep46 recovered through targeted checks if it did. Don't say the whole command47 passed when it didn't.48494. Push everything in one update. `ship:push` stages every publishable path,50 so first check `git status`: if a dirty path isn't part of this task, stop51 and leave it alone.5253 ```bash54 corepack pnpm ship:push -m "<subject naming the actual change>"55 ```5657 For an existing PR whose head isn't this branch on `origin`, push to the58 verified head repo and ref as `babysit-pr` describes. Don't open a second59 PR.60615. Merge immediately when the tree is clean and pushed, every review item is62 fixed or answered with a reply that was actually posted, and the PR isn't63 `CONFLICTING`. A reply you could only draft (someone else's PR, no comment64 permission) blocks the merge. Re-read the live PR as in `babysit-pr` step 165 (open, base `main`, and either yours or a PR the user named for this merge) and its `headRefOid`. It must equal66 `git rev-parse HEAD`, the head you validated and pushed. If it doesn't,67 someone pushed: redo steps 2-4. When they match, write it as68 `ship_merge_head_oid` and run:6970 ```bash71 gh pr merge <number> --squash --admin --match-head-commit <head-oid>72 ```7374 If the head moved, someone pushed. Redo steps 2-4 for the new head before75 you merge it. Don't wait for remote CI or release checks.76776. Fetch `origin/main` and confirm the merge commit is in it, then rotate with78 `/new-branch`'s post-merge step.7980## After the merge8182Because this path merged before remote CI finished, watch the workflows on83the merge commit:8485```bash86gh pr checks <number> # PR CI keeps running on the merged head87gh run list --commit <mergeCommit.oid> --limit 50 --json name,status,conclusion,url88```8990A failed query, or no runs listed yet, means unknown, not green. Keep checking until they finish.91Stop watching once the PR checks have all finished and the merge commit's92runs have finished, or successful queries have shown none for 10 minutes.93In that last case, report "no merge-commit runs seen", which is usually path94filters but unverified, rather than calling them green. Fix any failure on the fresh branch and send95it through `/ship`. If the PR body has a `Reports` section, run96`/review-latest-feedback` step 5 for those threads. Merging publishes beta97automatically. Beyond the merge commit's own workflows, beta, docs, and98release proof follow `ship-and-monitor`, when the user asks for it or a99concrete risk calls for it.