ci-validation-gates

Prevent CI/CD pipeline outages by enforcing defensive gatekeeping patterns like semantic versioning validation, NPM token checks, and draft release detection before publishing. This Skill intercepts invalid release states and environment configurations to stop failed deployments.

Validate an NPM_TOKEN as an Automation token by implementing a dedicated verification gate within your CI/CD pipeline. This check ensures the token has the correct permissions to bypass interactive prompts during automated publishing, preventing pipeline stalls.

Stop workflows from triggering on draft releases by implementing draft detection logic in your CI/CD pipeline. This gate checks the release state and prevents downstream build and deployment scripts from executing until the release is officially published.

Retry logic for npm registry propagation works by automatically re-attempting verification or publication steps after a delay. This mechanism handles temporary registry propagation delays, ensuring the published package is fully available before the pipeline completes.

Set SKIP_BUILD_BUMP before running a release build to protect build scripts from unintended version mutation. This environment variable enforces build script protection, ensuring the release version remains stable and consistent throughout the entire CI/CD process.

You can use this CI/CD validation gatekeeping on any pipeline using npm that requires robust release process validation. It is applicable across different version control systems as long as the deployment workflow relies on npm package publishing.