deploy-npm

Automate npm package publishing with package.json validation and semver gating.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jrc1883/popkit-claude --skill deploy-npm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-npm
Source: https://github.com/jrc1883/popkit-claude/tree/main/skills/pop-deploy-npm
Command: npx skills add https://github.com/jrc1883/popkit-claude --skill deploy-npm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardized npm publishing workflow with pre-publish checks, versioning, and automatic workflow generation.

Core Features & Use Cases

  • Package.json validation: ensure required fields and sensible defaults.
  • Workflow generation: creates CI workflow for publishing.
  • Safety: uses tokens and protects secrets during publish.

Quick Start

/popkit:deploy setup npm to generate publishing workflows.

Frequently Asked Questions about deploy-npm

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

FAQPage Schema
How do I automate npm package publishing with validation checks?

Automate npm package publishing by validating package.json, running tests, and gating releases through CI workflows. This Skill generates GitHub Actions workflows that enforce semver versioning, secure token handling, and pre-publish validation to prevent broken releases.

Can I publish scoped and private npm packages with automated workflows?

Yes. This Skill supports public, scoped, and private npm packages. It handles versioning, changelog integration, and secure token management for all package types, automating the entire publishing pipeline through generated CI workflows.

What pre-publish checks should I run before releasing an npm package?

Run package.json validation to verify required fields, execute test suites to ensure code quality, and use dry-run support to preview the publish step. These checks gate releases and prevent invalid or broken packages from reaching the registry.

How do I set up secure npm token handling in CI workflows?

Use npm tokens securely within generated GitHub Actions workflows by protecting secrets during publish. This Skill automates token configuration so credentials remain hidden while enabling authenticated publishing to npm registries.

Does this approach enforce semantic versioning for npm releases?

Yes. This Skill enforces semver versioning and validates version compliance before publish. It integrates with changelog management and restricts published files to ensure consistent versioning across releases.

What files get included or excluded when publishing an npm package?

This Skill restricts published files based on your configuration, allowing you to exclude development files, tests, and build artifacts. It ensures only necessary files reach the npm registry while validating package.json includes the correct file list.