ship

Solid

Verify and publish changes — push, open PR, watch CI until green; land mode merges an existing PR and cleans up. Triggers "ship it", "create PR", "open PR", "ready to merge", "/pr", "/ship", "push and PR", "watch the PR", "babysit CI", "loop until green"; land mode "land it", "/ship land", "fix CI and merge", "merge it then clean the branches", "merge and clean up".

AI & Automation 42 stars 3 forks Updated today MIT

Install

View on GitHub

Quality Score: 86/100

Stars 20%
54
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Ship Pipeline Before starting work, create a marker: `mkdir -p ~/.claude/tmp && echo "ship" > ~/.claude/tmp/heavy-skill-active && date -u +"%Y-%m-%dT%H:%M:%SZ" >> ~/.claude/tmp/heavy-skill-active` You are in **Maestro orchestration mode**. Execute the shipping checklist in order. ## Current State - Branch: !`git branch --show-current 2>/dev/null || echo "unknown"` - Working tree: !`git status --porcelain 2>/dev/null | head -20` - Recent commits: !`git log --oneline -5 2>/dev/null || echo "no commits"` ## Pipeline (All Steps Mandatory) ### Step 0: Preflight ```bash ssh-add -l ``` If no identities loaded: **Unlock 1Password and retry — git signing will fail otherwise.** Agent drops mid-flow are a recurring cause of failed pushes; catch it now, not after the commit. Do not commit until Steps 1–4 (typecheck/build/test/lint) are green. Skipping ahead is where amend churn comes from — `--amend` to fix a lint error you would have caught in 30 seconds invalidates signatures and CI runs. ### Step 1: Type Check ```bash bunx tsc --noEmit ``` If errors: fix them. Do not proceed until clean. ### Step 2: Build ```bash bun run build ``` If errors: fix them. Do not proceed until clean. ### Step 3: Test (if tests exist) **3a. Affected tests first (when `tldr` is available).** Run only the tests touched by your changes, before the full suite. Fast feedback if you broke something obvious: ```bash tldr change-impact --project . 2>/dev/null ``` If TLDR returns a list, run those test...

Details

Author
darkroomengineering
Repository
darkroomengineering/cc-settings
Created
7 months ago
Last Updated
today
Language
TypeScript
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

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
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.

0 Updated 1 months ago
RonenMars
AI & Automation Listed

ship

Ship the current changes as a merged pull request — branch off, run the project's tests, commit, open the PR, wait for CI, merge, and clean up the worktree. Runs a preflight first that marks each step RUN or SKIP, so a clean tree on the base branch exits without doing anything. Use when asked to ship it, ship this, land it, get this merged, open a PR and merge it, push this up and merge, 发出去, 合掉, 开个 PR 合了, 把这些改动提上去, 推上去合并. Not for tagging a release, publishing a package, deploying, or writing a commit message without pushing it.

0 Updated 3 days ago
Misoto22