vercel-labs / autoship

The CLI it wraps analyzes commits since the last version tag, suggests a patch, minor, or major bump, and writes the changeset description itself with AI. From there it opens a PR, waits for CI to pass, merges the changeset, waits for the Version Packages PR that the changesets GitHub Action generates, and merges that one too, which is what actually triggers the npm publish. It needs Node 18+, git, an authenticated GitHub CLI (gh auth login), and an AI_GATEWAY_API_KEY environment variable for the AI calls; multiple repositories can be registered with autoship add and picked from a list at release time.

If a project doesn't already use changesets, there is nothing here for it — the skill is a thin instruction layer over a CLI that assumes that workflow is already in place, not a general release manager. Its default behavior merges two separate pull requests and publishes to npm without a person confirming either step (a -y flag exists precisely to skip the prompts), which is worth knowing before pointing it at a production package rather than a test repository.

READ THE FULL ANALYSIS＋

This is Vercel's own tool for its own release workflow — Apache-2.0 licensed, one skill, 154 stars at the time of writing — not a package with breadth to describe beyond that single job.