skills.rest
chdaly
chdalyCOMMUNITY
Explore all skills by this author →
GitHub

ci-validation-gates

Automate defensive CI/CD checks for GitHub Actions and npm publish pipelines.

Updated Apr 10, 2026
Search Tags:#automation#security#semver#ci-cd#retry#token-verification#draft-release
One-click install
npx skills add https://github.com/chdaly/eshop --skill ci-validation-gates-chdaly
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci-validation-gates
Source: https://github.com/chdaly/eshop/tree/main/.copilot/skills/ci-validation-gates
Command: npx skills add https://github.com/chdaly/eshop --skill ci-validation-gates-chdaly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defensive CI/CD patterns to prevent release outages by catching invalid semver, incorrect tokens, missing retry logic, and draft releases before they reach customers.

Core Features & Use Cases

  • Semver Validation Gate: ensure version tags conform to semantic versioning.
  • NPM Token Type Verification: require Automation tokens for publishing to npm.
  • Retry Logic for Registry Propagation: wait and verify propagation after publish.
  • Draft Release Detection: ensure workflows trigger only on published releases.
  • Build Script Protection: disable accidental bumps during releases to avoid version drift.

Quick Start

Integrate these checks into your CI pipelines to guard every publish and release.

Frequently Asked Questions about ci-validation-gates

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

FAQPage Schema
How do I prevent invalid semver tags from triggering a faulty npm publish in GitHub Actions?▼

Semver validation gates prevent faulty npm publishes in GitHub Actions by checking version tags against semantic versioning rules before the release workflow proceeds. This guardrail blocks non-compliant tags from reaching the registry.

What is the best way to ensure CI workflows only trigger on published releases and ignore drafts?▼

Draft release detection ensures CI workflows trigger only on published releases by implementing release-state checks that explicitly ignore draft statuses. This prevents accidental deployments from incomplete GitHub release workflows.

How do I verify npm registry propagation after publishing a package in CI/CD?▼

To verify npm registry propagation after publishing, implement retry logic loops that wait and check the registry until the new version appears. This confirms the package is available before completing the CI workflow.

Does npm publishing in GitHub Actions require a specific token type to avoid failures?▼

Yes, npm publishing in GitHub Actions requires Automation tokens to avoid failures. Token verification gates check for the correct token type, preventing authentication errors and ensuring reliable automated publishes.

How do I stop accidental version bumps during a release build script to avoid version drift?▼

Build script protection stops accidental version bumps during releases by disabling automated version increments within the build process. This avoids version drift between the release tag and the published package.

Related Skills

Explore More Software Engineering Skills→
sachinnair90sachinnair90

ci-validation-gates

Validate semver, token types, retries, and draft-release triggers in GitHub Actions publish workflows.

Community
Advanced
NVIDIANVIDIA
33

availability-report

Verifies NVIDIA Elements npm packages and documentation site status, generating a report.

Official
Advanced
Leep-GHLeep-GH

ci-validation-gates

Automate CI/CD validation gates for semver, npm tokens, retries, and draft releases.

Community
Advanced
ronniegeraghtyronniegeraghty
3

ci-validation-gates

Enforce semver validation, token verification, retry logic, and draft-release detection in CI pipelines.

Community
Advanced