---
name: ship-pr
description: Take finished work in e2e-inc/e2e to a PR a human can review without fighting CI or bots - checks, verification against the built packages, a fresh-context self-review, the PR itself, then babysitting to the Ready for Human Review label. Use whenever you are asked to open, create, ship, or submit a PR, or when implementation is done and the next step is review.
metadata:
  internal: true
title: ship-pr
canonical_url: https://skilld.dev/gh/e2e-inc/e2e/ship-pr
last_updated: 2026-11-12T13:14:56.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/review-prompt.md](https://skilld.dev/api/skills-raw/e2e-inc/e2e/ship-pr/references/review-prompt.md).
>
> If the user asked to install this Skill, run `npx skilld install e2e-inc/e2e/ship-pr`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/ship-pr`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/e2e-inc/e2e/ship-pr) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/ship-pr`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/ship-pr --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/ship-pr --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Ship a PR

Opening a PR is not the finish line. The finish line is a PR labeled
`Ready for Human Review`: verified against the built packages, reviewed by a
fresh pair of eyes, green, and every bot thread handled. A human should only
ever spend time on judgment.

Run every step. If one cannot run, say which and why in the handoff instead
of skipping it quietly.

## 1. Checks

**Important:** first run the shortening pass from
[authoring-docs](../authoring-docs/SKILL.md#important-shorten-every-page) on
every guide page the change touches (`docs/**/*.mdx` outside
`docs/reference/`), even for a one-paragraph edit. A reference page the
change touches follows
[authoring-docs, Reference pages](../authoring-docs/SKILL.md#reference-pages)
instead: `## Reference` first, minimal summary tables, every fact kept. The
checks below then catch an anchor either pass broke.

Run what CI runs for what you touched, and fix everything:

```bash
pnpm check                    # lint, dead code, typecheck, error codes, peer ranges, docs
pnpm test                     # or the touched package: pnpm --filter e2e run test:unit
pnpm --filter @e2e-dev/testbed test
pnpm test:web-benchmark       # when the runner, web engine, or benchmark changed
```

Then the repo rules `pnpm check` cannot see (`AGENTS.md`, "Contracts"):

- A user-visible change to a published package adds a `.changeset/` entry,
  bumped `patch` on `0.x` even for a feature. `minor` only when the change is
  breaking (summary opens `**Breaking:**`) or the maintainer calls a big
  release (`**Release:**`).
- Behavior changes update the matching `docs/**/*.mdx` page in the same
  change, "not implemented yet" callouts included, and `skills/e2e/` when it
  describes the changed surface.
- A public API change reviews the emitted `.d.ts` and updates
  `packages/e2e/tests/types/sdk-types.ts`; a wire change edits the schema,
  both fixtures, and the producer together.
- A new build input or benchmark dependency goes into `.github/filters.yml`.
- A new integration, CI service, or migration guide gets the vendor's logo
  on every card that links to it, never a Font Awesome placeholder, and a
  card on its section's overview
  ([authoring-docs, Vendor logos](../authoring-docs/SKILL.md#vendor-logos)).
  A package PR needs this as much as a docs PR.

## 2. Verify

Prove the change with the [verify](../verify/SKILL.md) skill on the surface
it touches: the built CLI on the testbed or a benchmark, the MCP server, a
scratch project for `init`, or the docs site. Bug fixes capture main against
the branch. Keep the output and any video for the PR.

## 3. Self-review in a fresh context

The agent that wrote the change does not get to judge it. Spawn a reviewer
with no memory of this conversation (a subagent, or a new session) and give
it [references/review-prompt.md](https://skilld.dev/api/skills-raw/e2e-inc/e2e/ship-pr/references/review-prompt.md) with the base
branch filled in. Fix every `critical` and `important` finding you agree
with, then rerun steps 1 and 2 for what the fixes touched. For each finding
you reject, keep the one-line reason for the PR body or handoff.

No way to spawn a reviewer: re-read the whole diff cold against the same
prompt yourself, and say so in the handoff.

## 4. Commit and open

- Branch off an up-to-date `origin/main`. Commits follow Conventional
  Commits.
- Title and body with the [writing-pr](../writing-pr/SKILL.md) skill. The
  body carries the verification evidence from step 2.
- Open it ready, not draft:
  `gh pr create --base main --title ... --body-file <file> --attach <each screenshot and video>`
  (`gh` 2.99+). The body must carry the `## Verified` section `writing-pr`
  describes; fix a thin one with `gh pr edit --body-file <file> --attach ...`.
- Multi-PR change: open every layer, each based on the one below, before
  babysitting.

## 5. Babysit

Hand the PR to the [babysit](../babysit/SKILL.md) skill and run it to the
end: green, threads handled, `Ready for Human Review` label. For a stack,
babysit bottom-up; a layer is labeled only when it is ready on its own.

## Handoff

Reply to the human with:

- the PR URL and its label state
- how it was verified (surface, what you ran, what you saw, the media)
- what you fixed from review, what you dismissed and why
- anything left for them: escalated threads, parts you could not verify,
  scope you declined
