skills.rest
DeDuva
DeDuvaCOMMUNITY
Explore all skills by this author →
GitHub

release-process

Automate pre-release validation and npm publish commands for multi-package repositories.

1|Updated Apr 18, 2026
Search Tags:#workflow#npm#validation#release#publish#ci
One-click install
npx skills add https://github.com/DeDuva/squad --skill release-process-deduva
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-process
Source: https://github.com/DeDuva/squad/tree/main/packages/squad-sdk/templates/skills/release-process
Command: npx skills add https://github.com/DeDuva/squad --skill release-process-deduva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates pre-release validation, publish commands, and post-publish verification to ensure safe npm releases.

Core Features & Use Cases

  • Pre-release validation checks to prevent broken publishes.
  • Correct non-workspace npm publish commands for multi-package repos.
  • Fallback protocols when CI workflows fail and post-publish verification steps.

Quick Start

Initialize a release cycle in a test project to run validations and publish steps.

Frequently Asked Questions about release-process

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

FAQPage Schema
How do I automate npm publish commands for a multi-package repository?▼

To automate npm publish commands for a multi-package repository, apply correct non-workspace publish steps across dev, preview, and main release stages. This enforces versioning discipline and prevents broken package deployments.

What pre-release validation checks are needed to prevent broken npm publishes?▼

Pre-release validation checks to prevent broken npm publishes involve verifying package integrity and versioning discipline before executing the publish command. Applying these checks ensures post-publish smoke testing succeeds across multi-package repositories.

What is the fallback protocol when a CI workflow fails during an npm release?▼

When CI workflows fail during an npm release, a fallback protocol applies alternative publish commands to maintain deployment continuity. This ensures multi-package repositories still deploy safely while preserving versioning discipline and post-publish verification.

Can I run post-publish smoke testing across dev, preview, and main release stages?▼

Post-publish smoke testing can run across dev, preview, and main release stages. Executing these verification steps after publishing ensures multi-package repository deployments remain stable and broken npm releases are prevented.

How do I maintain versioning discipline during an npm release workflow?▼

Maintaining versioning discipline during an npm release workflow requires applying automated pre-release validation checks before executing publish commands. This process prevents broken releases by enforcing strict version control across multi-package repositories.

Related Skills

Explore More Software Engineering Skills→
remix-runremix-run
33.3k

publish-placeholder-package

Publish a minimal placeholder npm package at version 0.0.0 to reserve the package name.

Official
Intermediate
usepowershellusepowershell
9

Release Process

Validate package manifests and enforce release rules for npm monorepo publishes.

Community
Advanced
d-o-hubd-o-hub
4

npm-trusted-publishers

Validate npm OIDC trusted publishing configuration in GitHub Actions workflows.

Community
Advanced
AEtherlight-aiAEtherlight-ai

publish

Automate ÆtherLight release publishing to npm and GitHub.

Official
Intermediate