ship

Commit, push, and release agent-quorum changes through git, pnpm, GitHub Actions, and npm.

9|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/eventbalancer/agent-quorum --skill ship-eventbalancer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/eventbalancer/agent-quorum/tree/main/.agents/skills/ship
Command: npx skills add https://github.com/eventbalancer/agent-quorum --skill ship-eventbalancer

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about ship

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I commit and push changes in the agent-quorum repository?

Run /ship to trigger the change-set flow, which inspects the diff, runs pnpm verification checks, generates a conventional commit message linked to the originating GitHub issue, and pushes after you confirm the irreversible plan.

How do I publish a new npm version of agent-quorum?

Run /ship --release with patch, minor, major, or an explicit version. The release flow bumps the version with pnpm, validates with install, check, build, and publish dry-run, pushes a release commit, tags vX.Y.Z after main CI is green, and publishes via the GitHub Actions npm-publish approval.

Can I push directly to main without a pull request?

Yes, with /ship --to-main, but only if you are the ruleset bypass actor. The skill verifies bypass permission via the GitHub API, requires local pnpm run check to pass, and always demands explicit confirmation before the fast-forward push.

What happens when multiple git worktrees exist?

The worktree selection gate enumerates candidate session worktrees with branch, path, and task description, then acts only on the one you select. Done worktrees are skipped by default, and --worktree targets a specific branch or path explicitly.

Why does the build step run before lint and type checks?

The build regenerates dist/, which the type-aware lint and tests resolve through the package self-import. Running build concurrently would transiently delete those types and cause false lint failures, so it runs alone as a barrier before the concurrent check fan-out.