ci-validation-gates

Name: ci-validation-gates
Availability: InStock
Author: sudhakrms

Validate semver, token types, and draft releases in GitHub Actions workflows.

1|Updated Apr 17, 2026

Search Tags:#semver #github-actions #ci-cd #retry #npm-publish #draft-release #automation-token

Ready to run

npx skills add https://github.com/sudhakrms/CalendarControl --skill ci-validation-gates-sudhakrms

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ci-validation-gates
Source: https://github.com/sudhakrms/CalendarControl/tree/main/coffee/.copilot/skills/ci-validation-gates
Command: npx skills add https://github.com/sudhakrms/CalendarControl --skill ci-validation-gates-sudhakrms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents faulty CI/CD releases by validating semver formats, enforcing correct token types, adding retry logic for propagation, and detecting draft releases before publish.

Core Features & Use Cases

Semver validation gate integrated into publish workflows to reject invalid versions.
NPM token type verification to ensure Automation tokens are used for CI.
Retry logic for npm registry propagation to handle eventual consistency after publish.
Draft release detection to avoid triggering workflows on draft releases.
Build protection guidance to prevent accidental version bumps in development builds.

Quick Start

Integrate these gates into your CI workflow and start validating semver, tokens, and release state before publishing.

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 versions from being published in GitHub Actions?▼

To prevent invalid semver versions in GitHub Actions, you can integrate a semver validation gate into your CI workflow to automatically reject invalid version formats before an npm publish is triggered.

How do I handle npm registry propagation delays when publishing in CI?▼

To handle npm registry propagation delays in CI, implement retry logic that checks for registry consistency after publish, ensuring the package is fully available before downstream workflows proceed.

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

To stop GitHub Actions workflows from triggering on draft releases, implement draft-release detection gates that identify and block workflow execution when a release is still in draft state.

Do I need an automation token for npm publish in GitHub Actions CI?▼

Yes, npm publish in GitHub Actions CI requires an Automation token. You can enforce this by adding NPM token type verification to ensure standard publish or granular tokens are rejected.

Can I prevent accidental version bumps during development builds in CI?▼

Yes, you can prevent accidental version bumps during development builds by applying build protection guidance gates within your CI workflow that block version changes outside designated release paths.