Autoship

End to end npm release automation built around changesets. It creates a changeset (defaults to patch), runs an iterative fix loop for lint, types, tests, and formatting, commits and pushes, monitors CI with the Monitor tool, finds and auto-merges the Version Packages PR that changesets/action opens, then watches the publish workflow to completion. The safety model is interesting: invoking autoship is standing consent for the full flow, so it won't pause mid-release for confirmations. Instead it gates risky steps like PR merges behind objective preconditions (all checks green, title exactly matches "Version Packages"). Useful when you want to ship without babysitting seven different steps.

skills.sh installs: 687
GitHub stars: 191
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add mblode/agent-skills --skill autoship --agent claude-code

Installs into .claude/skills of the current project.

Files

Autoship

Drive an npm release end to end: changeset, fix loop, push, CI watch, Version Packages PR merge, publish watch, npm verification.

IS: the full release pipeline for an existing changesets-based npm package, from writing the changeset file to confirming the new version on the registry, plus diagnosing why a release run did not version or publish.
IS NOT: opening a feature PR (use pr-creator), monitoring a feature PR for reviews, conflicts, or CI (use pr-babysitter), general build or type fixes outside a release flow, or scaffolding a new package (use scaffold-cli, which hands off to autoship for the first release).