skills.rest
TokenRollAI
TokenRollAIOFFICIAL
Explore all skills by this author →
WebsiteGitHub

npm-publish

Automate npm package release with version bump, build, test, and 2FA publish.

49|8|Updated Mar 22, 2026
Search Tags:#publishing#npm#build#release#test#version-bump
One-click install
npx skills add https://github.com/TokenRollAI/acplugin --skill npm-publish-tokenrollai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: npm-publish
Source: https://github.com/TokenRollAI/acplugin/tree/main/.cursor/skills/npm-publish
Command: npx skills add https://github.com/TokenRollAI/acplugin --skill npm-publish-tokenrollai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates release management for the acplugin package, handling version bumps, builds, tests, and 2FA protected publishing to npm.

Core Features & Use Cases

  • Automated version bumps and changelog readiness during release.
  • Build and test orchestration to ensure a clean publish.
  • Dry-run packaging to verify artifacts before publishing to npm.
  • Guided 2FA publish flow with public package scope.

Quick Start

Run the release workflow to bump the version, build, test, pack, and publish acplugin with 2FA prompts.

Frequently Asked Questions about npm-publish

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

FAQPage Schema
How do I automate npm publish with version bump and tests?▼

Automating an npm publish with version bump and tests requires running `npm version`, `npm run build`, `npm test`, and `npm pack --dry-run` before executing `npm publish --access=public`. This ensures a clean, auditable release with verified artifacts.

How does 2FA work when publishing a package to npm?▼

2FA during an npm publish works by prompting for a One-Time Password (OTP) when you execute `npm publish --access=public`. This guided flow ensures that releases to public scopes are securely authenticated and auditable.

What is the safest way to release an npm package publicly?▼

The safest way to release an npm package publicly is to perform a dry-run package verification using `npm pack --dry-run` after passing build and test checks. This verifies the package artifacts before executing the actual publish.

Can I verify npm package artifacts before publishing to the registry?▼

Yes, you can verify npm package artifacts before publishing by running `npm pack --dry-run`. This process inspects the packaged files and confirms everything is correct before you trigger the final `npm publish` command.

Why should I run build and test before an npm version bump?▼

Running build and test before an npm version bump ensures that the code is stable and the package compiles correctly. This orchestration prevents publishing broken builds to the npm registry and maintains release safety.

Related Skills

Explore More Software Engineering Skills→
AutumnsGroveAutumnsGrove

npm-publish

Swaps registry to npm for publishing, then reverts to avoid conflicts.

Community
Advanced
SjdjdiejdrirhdkjejSjdjdiejdrirhdkjej

production-deployment-phase

Promote validated staging builds to production with semantic versioning and health checks.

Community
Advanced
hidonguyenhidonguyen

ck:test

Execute unit, integration, e2e, and UI tests across JavaScript/TypeScript, Python, Go, Rust, and Flutter projects.

Community
Advanced
shirulotshirulot

changelog-automation

Parse commit history to generate changelogs and release notes.

Community
Advanced