publish

Check, build, and publish a package to the npm registry.

1|Updated Feb 15, 2026

Search Tags:#npm #package management #build #release #pnpm #publish

Ready to run

npx skills add https://github.com/fabis94/fabis-ralph-loop --skill publish-fabis94

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: publish
Source: https://github.com/fabis94/fabis-ralph-loop/tree/main/.universal-ai-config/skills/publish
Command: npx skills add https://github.com/fabis94/fabis-ralph-loop --skill publish-fabis94

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of publishing a package to the npm registry, ensuring all necessary checks and builds are completed successfully.

Core Features & Use Cases

Prerequisite Validation: Checks for npm authentication and valid package metadata (repository, files).
Automated Checks & Build: Runs pnpm check and pnpm build to ensure code quality and successful compilation.
User Confirmation: Provides a summary and prompts for user approval before publishing.
Dry Run Option: Allows for a simulated publish to verify the process without actual deployment.

Quick Start

Use the publish skill to publish the current package to npm with a dry run.

Frequently Asked Questions about publish

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

FAQPage Schema

How do I automate publishing a package to the npm registry?▼

You can automate publishing a package to the npm registry by validating authentication, checking metadata, running build checks, and confirming deployment. This ensures a safe and streamlined release process.

Can I verify an npm package release without actually deploying it?▼

Yes, you can verify an npm package release without deploying by using a dry run. A dry run simulates the publish process, allowing you to validate checks and builds safely without actually pushing the package to the npm registry.

What npm package metadata is checked before a build and release?▼

Before a build and release, the package metadata checked includes the repository and files fields. Validating this metadata alongside npm authentication ensures the package is correctly configured for publishing to the registry.

Does the publish process work with pnpm for building and checking code?▼

Yes, the publish process works with pnpm by running pnpm check and pnpm build commands. This ensures code quality and successful compilation before the package is published to the npm registry.

What happens before the package is published to the registry?▼

Before the package is published to the registry, the process provides a summary of the upcoming deployment and prompts for user approval. This confirmation step ensures you maintain control over the actual release.