ci-validation-gates

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

3|5|Updated Mar 19, 2026

Search Tags:#semver #release-management #ci-cd #ci #token-verification #retry-logic #draft-detection

Ready to run

npx skills add https://github.com/ronniegeraghty/hyoka --skill ci-validation-gates-ronniegeraghty

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ci-validation-gates
Source: https://github.com/ronniegeraghty/hyoka/tree/main/.squad/templates/skills/ci-validation-gates
Command: npx skills add https://github.com/ronniegeraghty/hyoka --skill ci-validation-gates-ronniegeraghty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defensive CI/CD pipelines are prone to outages when semver formats are invalid, tokens are misused, or drafts slip into releases. This Skill provides a standardized set of checks and guardrails to prevent such failures.

Core Features & Use Cases

Semver Validation Gate: enforces correct version formats before publishing.
NPM Token Type Verification and Automation Tokens: ensures only automation tokens are used for CI tasks.
Retry Logic for Registry Propagation: handles eventual consistency after publish.
Draft Release Detection: prevents triggering workflows on drafts and misconfigured releases.
Build Script Protection: suggests environment flags to avoid unintended version bumps in releases.

Quick Start

Run this pattern in your CI workflow to enforce semver, token verification, retry logic, and draft-release checks.

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 semver formats in a GitHub Actions release workflow?▼

To validate semver formats in GitHub Actions, enforce a semver validation gate that checks version strings before publishing. This defensive pattern catches invalid version formats early in the CI pipeline to prevent failed deployments.

Why does my npm publish pipeline fail when using standard access tokens?▼

Npm publish pipelines fail when standard tokens are used because CI tasks require specific token types. Verifying npm token types ensures only automation tokens are used, preventing authentication errors during automated publishing.

What is the best way to handle npm registry propagation delays in CI/CD?▼

The best way to handle npm registry propagation delays is implementing retry logic for registry propagation. This pattern manages eventual consistency after a package publish by automatically retrying verification checks.

Can I prevent GitHub Actions workflows from triggering on draft releases?▼

Yes, you can prevent workflows from triggering on draft releases by implementing draft release detection. This guardrail checks release configurations to ensure drafts and misconfigured releases do not activate deployment pipelines.

How do I stop unintended version bumps during npm build scripts in CI?▼

To stop unintended version bumps during npm build scripts, apply build script protection using environment flags. This defensive pattern prevents automated release processes from accidentally modifying package versions.

Do I need defensive CI patterns for both GitHub Actions and npm publish pipelines?▼

Defensive CI patterns apply across both GitHub Actions workflows and npm publish pipelines. They enforce semver checks, token verification, retry logic, and draft detection to standardize release gates and prevent outages.