ci-validation-gates

Enforce CI/CD gates validating semver, NPM_TOKEN, and release events.

2|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/elbruno/md-to-slides --skill ci-validation-gates-elbruno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-validation-gates
Source: https://github.com/elbruno/md-to-slides/tree/main/.copilot/skills/ci-validation-gates
Command: npx skills add https://github.com/elbruno/md-to-slides --skill ci-validation-gates-elbruno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents CI/CD and release workflows from failing in costly ways due to invalid semver tags, incorrect npm token types, missing propagation retries, and accidental draft-release behavior.

Core Features & Use Cases

  • Semver Validation Gate: Enforces npm-compatible 3-part semver (and prerelease formats) before publish, rejecting invalid 4-part versions.
  • NPM Token Type Verification: Ensures NPM_TOKEN is an Automation token (not a user token requiring OTP) to avoid EOTP failures.
  • Retry Logic for Registry Propagation: Verifies published versions with bounded retries to handle eventual consistency delays after npm publish.
  • Draft Release Detection Guardrails: Promotes publishing only from GitHub release events that actually fire (e.g., release published), and adds checks for workflow_dispatch scenarios.
  • Build Script Protection: Requires SKIP_BUILD_BUMP=1 during release builds to avoid silent version mutation from bump-build scripts.

Quick Start

Ask an AI to generate a GitHub Actions workflow step-by-step that applies semver validation, verifies NPM_TOKEN is automation-grade, retries npm verification up to 5 times with 15-second intervals, and only proceeds on release-published events while setting SKIP_BUILD_BUMP=1 for release builds.

Frequently Asked Questions about ci-validation-gates

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

FAQPage Schema
Why does npm publish fail with EOTP errors in GitHub Actions workflows?

npm publish fails with EOTP errors when using a user token instead of an Automation token. Verifying NPM_TOKEN type in your CI gates ensures it is automation-grade, preventing interactive OTP prompts from blocking release workflows.

How do I verify npm registry propagation after publishing a package?

Verify npm registry propagation by implementing bounded retry logic for npm view checks after publish. This handles eventual consistency delays by retrying verification up to 5 times with 15-second intervals to confirm the published version exists.

How do I prevent draft release events from triggering npm publish workflows?

Prevent draft release triggers by adding detection guardrails that promote publishing only from GitHub release-published events. These CI checks ensure workflows do not proceed on draft releases or unexpected workflow_dispatch scenarios.

How do I stop version mutation during npm release builds in GitHub Actions?

Stop version mutation during npm release builds by requiring the SKIP_BUILD_BUMP environment variable to equal 1. This build script protection guards against silent version changes caused by bump-build scripts within CI pipelines.