What problem does it solve? Shipping repository changes safely requires coordinating git staging, verification, PR reconciliation, and npm releases without skipping gates or rewriting history. This Skill enforces a disciplined delivery workflow so commits, pushes, tags, and publishes happen in the correct order with explicit confirmation before every irreversible step. ## Core Features & Use Cases - Change-set flow: Verify, commit, and push dirty changes to a new branch, an existing PR branch, or directly to main with ruleset-bypass guardrails, then mark the session worktree done. - Release flow: Execute version bumps, release commits, tags, GitHub Actions publish approval, npm verification, and GitHub Release creation following docs/release.md. - Parallel verification fan-out: Run a build barrier followed by concurrent types, lint, format, and test workers while delegating read-only diff and commit-message preparation to sub-agents. - Use Case: After finishing a feature on a session branch, run /ship to verify the change with pnpm checks, generate a conventional commit linked to its GitHub issue, push the branch, and update the open PR. ## Quick Start Ask the agent to run /ship to verify, commit, and push the current dirty changes in the agent-quorum repository.