ci-validation-gates

Validate Semver, token types, and retry registry propagation in CI/CD pipelines.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/barichter/squad --skill ci-validation-gates-barichter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-validation-gates
Source: https://github.com/barichter/squad/tree/main/.copilot/skills/ci-validation-gates
Command: npx skills add https://github.com/barichter/squad --skill ci-validation-gates-barichter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires npm, and includes scripts (resource) components.

What problem does it solve?

This Skill ensures that your continuous integration/continuous delivery (CI/CD) pipelines are resilient against common issues by implementing crucial validation, retry, and security patterns.

Core Features & Use Cases

  • Semver Validation: Validates semver (Semantic Versioning) compliance for npm publications.
  • Token Type Verification: Ensures that npm tokens are of the correct type (Automation tokens without 2FA).
  • Retry Logic: Implements retry mechanisms for npm registry propagation, ensuring consistent package verification.
  • Draft Release Detection: Prevents workflows from proceeding on draft releases.
  • Build Script Protection: Protects against unintended version mutations during release builds.

Quick Start

Initialize the ci-validation-gates skill in your project repository and apply it to your release workflows.

Frequently Asked Questions about ci-validation-gates

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

FAQPage Schema
How do I validate npm tokens and prevent CI/CD pipeline failures during package publishing?

To validate npm tokens and prevent pipeline failures, this Skill verifies that npm tokens are Automation tokens without 2FA and validates Semver compliance before publication. This ensures reliable CI/CD workflows by blocking invalid configurations early.

What is the best way to handle npm registry propagation delays in automated release workflows?

The best way to handle npm registry propagation delays is implementing retry logic for package verification. This Skill applies retry mechanisms to ensure consistent package verification after publication, resolving timing issues in CI/CD pipelines.

How do I stop GitHub Actions or CI workflows from running on draft releases?

To stop CI workflows from running on draft releases, this Skill implements draft release detection to prevent workflows from proceeding. It blocks pipeline execution when a draft release is identified, saving unnecessary build runs.

Can I use ci-validation-gates to protect against unintended version mutations in my build scripts?

Yes, you can use this Skill to protect against unintended version mutations in build scripts. It provides build script protection specifically designed to secure your CI/CD pipelines against accidental version changes during release builds.

Do I need npm installed to implement Semver validation and retry logic in my CI/CD pipelines?

Yes, you need npm installed as a dependency to implement Semver validation and retry logic in your CI/CD pipelines. The Skill operates as scripts within your project repository to validate npm publications and registry propagation.