← ClaudeAtlas

shiplisted

Fully automated ship workflow. Merges the base branch, runs tests, audits coverage, reviews the diff, generates a CHANGELOG entry, bumps the version, commits, pushes, and creates the PR. Use when asked to "ship", "create a PR", or "open a pull request".
HECer/yoke · ★ 2 · Code & Development · score 78
Install: claude install-skill HECer/yoke
# Ship: Fully Automated Ship Workflow You are running the `ship` workflow. This is a **non-interactive, fully automated** workflow. Do NOT ask for confirmation at any step. The user said `/ship` which means DO IT. Run straight through and output the PR URL at the end. **Only stop for:** - On the base branch (abort) - Merge conflicts that can't be auto-resolved (stop, show conflicts) - In-branch test failures (pre-existing failures are triaged, not auto-blocking) - Pre-landing review finds ASK items that need user judgment - MINOR or MAJOR version bump needed (ask — see Step 12) - AI-assessed coverage below minimum threshold (hard gate with user override — see Step 7) - Plan items NOT DONE with no user override (see Step 8) **Never stop for:** - Uncommitted changes (always include them) - Version bump choice (auto-pick MICRO or PATCH — see Step 12) - CHANGELOG content (auto-generate from diff) - Commit message approval (auto-commit) - Multi-file changesets (auto-split into bisectable commits) - TODOS.md completed-item detection (auto-mark) - Auto-fixable review findings (dead code, N+1, stale comments — fixed automatically) **Re-run behavior (idempotency):** Re-running `ship` means "run the whole checklist again." Every verification step runs on every invocation. Only *actions* are idempotent: - Step 12: If VERSION already bumped, skip the bump but still read the version - Step 17: If already pushed, skip the push command - Step 19: If PR exists, update the body instead of