agentsclimarketplace
Sign in

Ship

Skill kreek/consult/.agents/skills/ship

Run Consult's guarded maintainer flow for commit, merge, version bump, validation, and push.From its SKILL.md

Install
npx -y skills add kreek/consult --skill ship

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.2 KB, 737 tokens by cl100k_base, as published. Nobody here has run it

Ship

When to Use

  • Use when the user asks to ship this Consult repository or explicitly invokes $ship.
  • Use only for this repository's maintainer release flow: commit, merge to main, bump release artifacts, validate, and push.

When NOT to Use

  • Do not use for ordinary commits; use the commit skill instead.
  • Do not use for release preparation by itself; use the release skill.
  • Do not use outside this repository.

Iron Law

DO NOT RUN THE WHOLE SHIP FLOW UNATTENDED; STOP AT EVERY CONFIRMATION GATE.

Repo Facts

  • Main branch is main; remote is origin.
  • There are two independent release streams. Never bump them in lockstep.
  • Plugin version lives in plugin/.claude-plugin/plugin.json, plugin/.codex-plugin/plugin.json, plugin/.cursor-plugin/plugin.json, .claude-plugin/marketplace.json, and .cursor-plugin/marketplace.json. plugin/plugin.json should match these too; reconcile drift when bumping.
  • The consult npm package version lives in consult/package.json. Bump it only when the diff changes the published package.
  • Root package.json is private tooling and is not versioned for release.
  • Version marker is the CHANGELOG.md header ## [X.Y.Z] (YYYY-MM-DD). Promote ## [Unreleased] into a dated version section and leave a fresh empty ## [Unreleased] above it.
  • Releases are not git-tagged in this repo. Do not create or push a tag unless the user explicitly asks.
  • Commit messages use imperative subjects and no author-attribution trailers.

Workflow

  1. Pre-flight: run git status and git rev-parse --abbrev-ref HEAD. If the working tree is clean and already on main, report that there is nothing to ship and stop.
  2. Commit: review git diff and git diff --cached, group uncommitted changes into logical commits, propose the grouping, and get user approval before committing on the current branch.
  3. Merge to main, only when not already on main: run git fetch origin, bring main up to date, get user approval, then merge the current branch into main. On conflicts, stop and show the conflicted files.
  4. Bump the version on main: use the release skill to classify the bump from the merged diff, or use the user's explicit patch, minor, or major override. Confirm the proposed version before writing. Update the relevant release artifacts and commit the bump as Release <version>.
  5. Validate and push: run the project validation gate before pushing. Abort on failure. Get user approval before git push origin main.

Before Saying Done

Report the branch shipped, merge result, old and new version per release stream, validation result, pushed commit, skipped release streams, and any remaining publishing or plugin-sync work.

Verification

  • The skill stopped at each approval gate before committing, merging, versioning, and pushing.
  • Release-stream bumps matched the actual changed surface.
  • CHANGELOG.md and every relevant manifest agreed after the version bump.
  • Validation ran before push, or the skipped validation is clearly reported.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most ship operate skills give in 737 tokens

Counted across 1,077 of the 1,713 authors here whose files we hold, read 2026-09-06

  • Create GitHub releasein 44 of 1077, across 43 files
  • Run the test suitein 30 of 1077, across 25 files
  • Create and push git tagin 27 of 1077, across 26 files
  • Push commits and tagsin 27 of 1077
  • Create annotated tagin 25 of 1077, across 22 files
  • Ensure working tree is cleanin 24 of 1077
  • Check for product marketing context firstin 23 of 1077, across 6 files
  • Commit version bump changesin 22 of 1077, across 21 files
  • Update CHANGELOG.mdin 21 of 1077, across 20 files
  • Structure launch marketing across three channel typesin 20 of 1077, across 5 files
  • Commit and tag the releasein 20 of 1077, across 18 files
  • Update the CHANGELOG for new releasesin 19 of 1077

Said here and by no other author read

  • Stop at every confirmation gate
  • Run git status and git rev-parse
  • Merge the current branch into main
  • Update the relevant release artifacts

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.