Release Process

Automate npm package releases with dependency validation and post-publish verification.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/nicolehaugen/CustomMetricsDashboard --skill release-process-nicolehaugen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Release Process
Source: https://github.com/nicolehaugen/CustomMetricsDashboard/tree/main/.squad/templates/skills/release-process
Command: npx skills add https://github.com/nicolehaugen/CustomMetricsDashboard --skill release-process-nicolehaugen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the release process for npm packages, ensuring smooth and error-free publishes by providing pre-release checks, fallback procedures, and post-publish verification steps.

Core Features & Use Cases

  • Pre-release Validation: Checks for workspace leaks, incorrect dependencies, and non-semver version strings.
  • Fallback Procedures: Handles CI workflow failures with retry and local publish options.
  • Post-Publish Verification: Ensures correct package versions and smoke tests after publication.

Quick Start

Run the release process skill to automate the release of your npm package following the defined rules and procedures.

Frequently Asked Questions about Release Process

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

FAQPage Schema
How do I automate the npm package release process with validation and verification?

You can automate the npm package release process by running a skill that handles dependency validation, semantic versioning adherence, and post-publish verification to ensure package integrity.

What checks are needed before publishing an npm package to prevent workspace leaks?

Pre-release validation for npm packages should check for workspace leaks, incorrect dependencies, and non-semver version strings to ensure error-free publishes.

How do I handle CI workflow failures during an npm package release?

Handle CI workflow failures during an npm package release by using fallback procedures that offer retry options and local publish capabilities.

What is the best way to verify package integrity after publishing to npm?

The best way to verify package integrity after publishing to npm is by running post-publish verification steps that check for correct package versions and perform smoke tests.

Do I need semantic versioning for my npm package release workflow?

Yes, semantic versioning adherence is required for npm package release workflows to validate version strings and maintain structured release procedures.

Why does my npm package release fail dependency validation checks?

Npm package releases fail dependency validation when pre-release checks detect workspace leaks, incorrect dependencies, or version strings that do not adhere to semantic versioning.