skills.rest
tillysoso
tillysosoCOMMUNITY
Explore all skills by this author →
GitHub

autoship

Automate npm release workflows with changesets and CI monitoring.

Updated Sep 10, 2025
Search Tags:#automation#git#npm#release#ci#changesets#autoship
One-click install
npx skills add https://github.com/tillysoso/mv1 --skill autoship-tillysoso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: autoship
Source: https://github.com/tillysoso/mv1/tree/main/.claude/skills/autoship
Command: npx skills add https://github.com/tillysoso/mv1 --skill autoship-tillysoso

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates npm release workflows using changesets and CI monitoring to ship npm packages.

Core Features & Use Cases

  • Create changesets, fix quality issues, and commit/push
  • Monitor CI and merge the Version Packages PR
  • Watch the release workflow to completion across the pipeline

Quick Start

Run the autoship workflow on your npm package to perform a default patch release with a changeset

Frequently Asked Questions about autoship

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

FAQPage Schema
How do I automate npm package releases with changesets from start to finish?▼

You can automate npm package releases by creating a changeset, fixing lint issues, committing and pushing, monitoring CI, merging the Version Packages PR, and watching the publish workflow to completion. This handles the full release cycle end-to-end.

What is the Version Packages PR workflow in changesets?▼

The Version Packages PR workflow in changesets consolidates pending changesets into version bumps and changelog updates. It requires monitoring CI pipelines and merging the PR to trigger the final npm publish workflow.

Do I need a CI pipeline configured to automate npm publishing?▼

Yes, automating npm publishing requires a CI pipeline to monitor. The workflow watches CI status before merging the Version Packages PR and tracks the publish workflow to confirm the package ships successfully.

Can I monitor CI status and merge pull requests automatically for npm releases?▼

You can monitor CI status and merge the Version Packages PR automatically as part of the npm release workflow. It tracks CI pipelines and proceeds to merge once checks pass, then watches the publish workflow.

What's the best way to handle linting and fixing code before an npm release?▼

Before an npm release, linting and fixing code quality issues is handled automatically within the workflow. It creates a changeset, applies lint fixes, then commits and pushes the changes before monitoring CI.

Why does my changesets publish workflow fail after merging the Version Packages PR?▼

A changesets publish workflow can fail after merging if CI checks were not fully passed or if publish permissions are misconfigured. The workflow monitors CI before merging and watches the publish workflow to catch completion issues.

Related Skills

Explore More Software Engineering Skills→
vecearvecear

release-automation-builder

Automate releases, changelogs, git tags, and npm publishing with changesets or semantic-release.

Community
Advanced
AstorYHAstorYH
15

npm-package-version

Empower your project with effortless dependency updates. Our tool scans npm for outdated packages and upgrades them to the latest stable versions, ensuring your software stays secure, efficient, and maintainable. Perfect for developers who want to keep dependencies fresh without sacrificing productivity.

Community
Basic
leanEthereumleanEthereum
143

checks

Run linting, formatting, type, spell, and Markdown checks with ruff, ty, codespell, and mdformat.

Official
Intermediate
tneztnez

release-package

Create and publish new npm package versions with changelog updates.

Community
Intermediate