ci-validation-gates

Automate CI/CD validation gates for semver, token types, retries, and draft releases.

Updated Aug 23, 2026

Search Tags:#automation #workflow #semver #ci-cd #retry #token #draft-release

Ready to run

npx skills add https://github.com/CarlosSardo/nats-poc-simulator --skill ci-validation-gates-carlossardo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ci-validation-gates
Source: https://github.com/CarlosSardo/nats-poc-simulator/tree/main/.copilot/skills/ci-validation-gates
Command: npx skills add https://github.com/CarlosSardo/nats-poc-simulator --skill ci-validation-gates-carlossardo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defensive CI/CD practices prevent release disasters by enforcing correct versioning, ensuring tokens are automation-based, and guarding against draft releases. This reduces outages and speeds up safe deployments.

Core Features & Use Cases

Semver Validation Gate: Ensure version strings conform to semantic versioning before publish.
NPM Token Type Verification: Enforce the use of automation tokens rather than user tokens with 2FA.
Retry Logic for Propagation: Implement retries to account for eventual consistency after publish.
Draft Release Detection: Ensure workflows trigger on release: published events.
Use Case: Use within npm package release pipelines to validate and gate the release.

Quick Start

Configure your CI workflow to run the Semver Validation Gate and Token Type Verification steps before any publish step.

Frequently Asked Questions about ci-validation-gates

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

FAQPage Schema

How do I enforce semver validation in CI/CD pipelines before publishing an npm package?▼

Semver validation in CI/CD pipelines enforces semantic versioning correctness by implementing explicit validation gates that check version strings before any npm publish step. This prevents releasing packages with invalid version formats.

How do I verify npm automation tokens versus user tokens in GitHub Actions release workflows?▼

NPM token type verification enforces the use of automation tokens rather than user tokens with 2FA in release workflows. This validation gate checks token types within your CI steps to prevent authentication failures during automated npm publishing.

Why does my npm publish workflow fail due to eventual consistency, and how do I add retry logic?▼

Retry logic for eventual consistency addresses npm publish propagation delays by implementing automated retry patterns after the initial publish step. This ensures downstream CI steps wait for registry updates before attempting dependent operations.

How do I configure GitHub Actions to trigger workflows only on release published events and skip drafts?▼

Draft release detection ensures GitHub Actions workflows trigger exclusively on release: published events. Configuring this detection logic prevents CI pipelines from accidentally running publish steps on draft or unready releases.

Can I use these defensive CI/CD validation gates for Docker package publishing workflows?▼

Yes, defensive CI/CD validation gates apply to Docker and other package publishing workflows beyond npm. The validation logic integrates into standard YAML steps across various package and publish workflows to harden releases.

What are defensive CI/CD patterns and when do I need them for automated release pipelines?▼

Defensive CI/CD patterns are validation gates and retry mechanisms that prevent release outages by enforcing versioning and token correctness. You need them in automated release pipelines where guarding against invalid versions or misused tokens is critical.