ship-pr
Verify each PR in an isolated worktree, run simplify, and open it with gh. Use for completed work ready for review; use bare gh pr create if those passes are unnecessary, or watch-pr for an open PR.
Cynnamoroll · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add Cynnamoroll/factory-stack --skill ship-prAbout this skill
name: ship-pr description: "Verify each PR in an isolated worktree, run simplify, and open it with gh. Use for completed work ready for review; use bare gh pr create if those passes are unnecessary, or watch-pr for an open PR." license: MIT compatibility: droid disable-model-invocation: true
Ship PR
Open cleaned-up PRs, independently verified and described in one minute of reading.
1. Shape the commits
Rebase into small, ordered commits. Each future PR lands on its own and the order tells the story: the failing test before the fix, the removal before the reshape. Prefer several narrow PRs to one large one. Stage only your files (git add <files>).
A stack is a chain of base branches. The bottom PR targets the default branch, and each child targets its parent's branch.
2. Verify each PR independently
Verify each PR branch in a fresh run and worktree, separate from its author:
droid exec -m auto --auto medium --worktree "verify-<branch>" -o json \
"Check out <branch>. Run /prove-it-works on the change between <base> and <branch>. End with PASS, PASS+NOTES, or FAIL and the evidence."
Run several with & and wait. CI and bot approval do not replace a user-path run. Return a FAIL to the author; do not open that PR.
Record the verified commit. After a rebase, compare git diff <base>...<verdict-sha> | git patch-id --stable with the current head's patch ID. Reverify if they differ.
If droid exec fails on authentication, ask the user to export FACTORY_API_KEY in their shell. Never write a key to a file.
3. Clean the diff
Run Droid's built-in simplify skill on each PR's diff and apply the fixes that hold up. Remove comments that narrate steps. Rerun prove-it-works if simplify changed behavior-bearing code.
4. Write the PR
- Title. Conventional Commits,
type(scope): subject, imperative, no trailing period, naming a real symbol when one carries the change. - Body. Run
tighten-proseon it. Use##headings in this order and drop any with nothing to say:## Why: the problem and approach in 1 to 3 sentences.## What changed: 1 to 3 bullets.## Scope: what it covers and what it leaves out.## Tradeoffs: only rejected alternatives a reviewer would ask about.## Blast radius: who or what it touches and why that is safe or risky.## Verification: the verdict and 1 to 3 run paths with outcomes. Perf gets one number, before and after.
Write the body to a file. Open the PR ready, not draft:
gh pr create --base <base> --head <branch> --title "<title>" --body-file /tmp/pr-body.md
Then read it back with gh pr view <number>.
Done when
Every PR opened has a PASS or PASS+NOTES verdict whose patch ID matches its head, simplify ran on its diff, and the reply lists each PR as a full https://github.com/<owner>/<repo>/pull/<number> URL with its verdict. Opening a PR does not start a watch. The user runs /watch-pr when the stack is complete. Remove the verify-* worktrees when done.