ci-validation-gates

Enforces semantic versioning and validates npm tokens in CI/CD pipelines.

Updated May 10, 2026

Search Tags:#version control #CI/CD #retry logic #token validation #pipeline security

Ready to run

npx skills add https://github.com/AshleyHollis/agentic-identity-lab --skill ci-validation-gates-ashleyhollis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ci-validation-gates
Source: https://github.com/AshleyHollis/agentic-identity-lab/tree/main/.copilot/skills/ci-validation-gates
Command: npx skills add https://github.com/AshleyHollis/agentic-identity-lab --skill ci-validation-gates-ashleyhollis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents common CI/CD outages by implementing defensive patterns for semantic versioning, token checks, retry logic, and draft detection.

Core Features & Use Cases

Semver Validation Gate: Ensures valid version format before publishing to npm.
NPM Token Type Verification: Validates NPM_TOKEN as an Automation token.
Retry Logic: Implements retry logic for npm registry propagation.
Draft Release Detection: Detects draft releases and prevents workflows from triggering on them.
Build Script Protection: Sets SKIP_BUILD_BUMP before release builds to prevent version mutation.

Quick Start

Run the skill to validate the release process in your CI/CD pipeline.

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 CI/CD pipeline outages caused by invalid npm releases?▼

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.

What's the best way to validate an NPM_TOKEN is an Automation token in a CI/CD pipeline?▼

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.

How do I stop GitHub Actions workflows from triggering on draft releases?▼

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.

How does retry logic for npm registry propagation work during a release?▼

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.

Why do I need to set SKIP_BUILD_BUMP before running a release build?▼

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.

Can I use this CI/CD validation gatekeeping on any version control pipeline?▼

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.