pr-ship

Solid

End-to-end PR lifecycle: create PR, wait for CI, review, fix issues, merge - all in one invocation. Use when: (1) User says "/pr-ship", (2) User wants to ship current changes as a complete PR lifecycle, (3) User wants to resume shepherding an existing PR.

AI & Automation 604 stars 115 forks Updated 3 days ago AGPL-3.0

Install

View on GitHub

Quality Score: 85/100

Stars 20%
93
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# PR Ship End-to-end PR lifecycle shepherd: create PR → wait for CI → review → fix → merge. Single invocation, single PR. **Announce at start:** "Using pr-ship skill to shepherd this PR from creation to merge." ## Usage ``` /pr-ship [pr_number] [--no-auto-merge] ``` | Parameter | Default | Description | | ----------------- | ------- | ------------------------------------------------------------ | | `pr_number` | none | Resume from an existing PR (skip creation) | | `--no-auto-merge` | off | Require user confirmation before merge instead of auto-merge | ## Session State Track these values in conversation context throughout the session: - `PR_NUMBER` - current PR number - `PHASE` - current phase (create / ci-wait / review / fix / merge) - `RETRY_COUNT` - CI failure + review fix retry counter (max 3, shared), initialized to 0 - `AUTO_MERGE` - true unless `--no-auto-merge` is passed - `EMPTY_CI_COUNT` - consecutive empty CI check counter (max 3), initialized to 0 --- ## Phase 0 - Create PR **Skip if `pr_number` is provided.** When skipping, set `PR_NUMBER` from the argument and jump to Phase 1. **Parse arguments:** ```bash # Detect --no-auto-merge flag AUTO_MERGE=true if echo "$ARGUMENTS" | grep -q -- '--no-auto-merge'; then AUTO_MERGE=false fi # Detect pr_number (first numeric argument) PR_NUMBER=$(echo "$ARGUMENTS" | grep -oE '[0-9]+' | head -1) ``` **If `PR_NUMBER` is set:*...

Details

Author
FerroxLabs
Repository
FerroxLabs/wayland
Created
3 months ago
Last Updated
3 days ago
Language
TypeScript
License
AGPL-3.0

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

ship

Open a PR and merge it in one step — combines `bin/pr.sh` create with `bin/wait-for-pr-checks.sh` polling and `gh pr merge`. Default mode enables GitHub's native auto-merge so the terminal returns immediately; `--client-side` polls in the foreground and merges when CI goes green. TRIGGER when the user says "ship this PR", "ship it", "open and merge", "PR and merge", "create PR and auto-merge it", "wait for CI then merge", "block until merged", "/nyann:ship". Do NOT trigger on "open a PR" alone (no merge intent) — that's the `pr` skill. Do NOT trigger on "merge this existing PR #N" — ship is PR-creation + merge, not standalone merge of an already-open PR. Do NOT trigger on "release X.Y.Z" — that's the `release` skill, which tags a merged commit rather than creating one.

6 Updated 1 weeks ago
thettwe
AI & Automation Listed

ship-pr

Ship a single change through a worktree -> branch -> PR -> squash-merge -> cleanup workflow - pick the right branch type (feat/fix/chore/docs/hotfix), implement, verify with this repo's real build/typecheck/test commands, open the PR, check CI, merge, and clean up. Use for any single PR-sized change in any git repo with a GitHub remote - a bug fix, a small feature, a doc edit, a dependency bump. For 3+ independently shippable PRs from one analysis pass, see parallel-ship. For sequential phases where each PR builds on the last, see epic-ship.

2 Updated 1 months ago
davidtheproduct
Code & Development Listed

ship

Push a committed feature branch, open a PR, watch CI, and (only on explicit confirmation) squash-merge and clean up. Use when the user says "ship this", "push and open a PR", "is CI green yet", or asks to merge a PR that's already open. Assumes the branch is already committed — this skill does not stage or commit anything. Does not require ending at a merge: an open, CI-green PR is a valid stopping point.

1 Updated 1 months ago
RonenMars