ship

Runs a gated maintainer flow for committing, merging, versioning, validating, and pushing releases.

1|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/kreek/consult --skill ship-kreek
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/kreek/consult/tree/main/.agents/skills/ship
Command: npx skills add https://github.com/kreek/consult --skill ship-kreek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping a release involves many error-prone steps: grouping commits, merging to main, bumping versions across multiple manifests, updating the changelog, validating, and pushing. This Skill enforces a guarded, approval-gated maintainer flow so no irreversible step happens without explicit human confirmation. ## Core Features & Use Cases - Approval-gated release flow: Stops for user confirmation before committing, merging, version bumping, and pushing, so nothing ships unattended. - Dual release stream handling: Independently bumps the plugin manifests (plugin.json, marketplace.json) and the npm package version only when their actual surfaces changed, keeping CHANGELOG.md in sync. - Validation before push: Runs the project validation gate and aborts on failure before pushing to origin main. - Use Case: After finishing a feature branch in the Consult repository, invoke the ship flow to review the diff, approve logical commit groupings, merge to main, bump the minor version, validate, and push with confirmation at each gate. ## Quick Start Ask the agent to ship this repository using the ship skill and confirm each approval gate as it appears.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I ship a release with approval gates in git?▼

Invoke the ship skill, which walks through pre-flight checks, commit grouping, merge to main, version bumping, validation, and push. It stops for explicit user approval before each irreversible step so nothing ships unattended.

How to bump versions across multiple plugin manifests consistently?▼

The flow updates plugin.json files, marketplace.json files, and package.json independently per release stream, then reconciles drift so all manifests and the CHANGELOG.md version header agree before committing the bump.

When should I use the ship skill instead of a normal commit?▼

Use ship only for the full maintainer release flow of this repository: commit, merge to main, version bump, validate, and push. For ordinary commits use the commit skill, and for release preparation alone use the release skill.

Does the ship flow create git tags for releases?▼

No. Releases in this repository are not git-tagged, and the flow will not create or push a tag unless the user explicitly asks for one.

What happens if validation fails before pushing a release?▼

The flow aborts the push when the project validation gate fails. The failure is reported, and no push to origin main occurs until validation passes and the user approves.