skills.rest
olivomarco
olivomarcoCOMMUNITY
Explore all skills by this author →
Website𝕏@olivomarcoGitHub

ci-validation-gates

Automate semver validation, npm token verification, and release pipeline checks.

66|41|Updated Mar 4, 2026
Search Tags:#semver#ci-cd#retry#defensive#token-verification#draft-release
One-click install
npx skills add https://github.com/olivomarco/vbd-copilot --skill ci-validation-gates-olivomarco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci-validation-gates
Source: https://github.com/olivomarco/vbd-copilot/tree/main/.copilot/skills/ci-validation-gates
Command: npx skills add https://github.com/olivomarco/vbd-copilot --skill ci-validation-gates-olivomarco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CI/CD pipelines often release with defects due to invalid versions, incorrect tokens, lack of retry propagation, and silent draft releases. This Skill provides a set of defensive patterns to guard the release process and ensure only valid, verifiable artifacts are published.

Core Features & Use Cases

  • Semver Validation Gate: validates version formats before publish to prevent mangled versions.
  • NPM Token Type Verification: enforces Automation tokens and avoids OTP-based user tokens in CI.
  • Retry Logic for Propagation: retries after publish to handle eventual consistency across registries.
  • Draft Release Detection: ensures workflows only proceed when releases are truly published.
  • Build Script Protection: prevents accidental version bumps or mutations during release.

Quick Start

Enable the defensive checks in your CI by adding a semver gate, token verification, propagation retry, and draft-release guard to your release pipelines.

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 CI/CD pipelines?▼

Semver validation gates prevent invalid versions from being published by checking version formats before npm publish workflows or container builds proceed. This defensive CI/CD pattern ensures only correctly formatted releases reach the registry.

Why does my npm publish workflow fail when using a user OTP token instead of an automation token?▼

npm publish workflows fail with user OTP tokens because CI environments require automation tokens for non-interactive authentication. NPM token type verification enforces automation tokens to avoid OTP-based user tokens blocking release pipelines.

Can I add retry logic to npm publish workflows to handle registry propagation delays?▼

Retry logic for propagation handles eventual consistency across registries by automatically retrying after publish. This defensive pattern ensures workflows only proceed when releases are truly published and propagated.

How do I detect draft releases and stop CI/CD pipelines from deploying unpublished versions?▼

Draft release detection stops CI/CD pipelines from deploying unpublished versions by ensuring workflows only proceed when releases are truly published. This guard prevents silent draft releases from triggering faulty downstream deployments.

What is the best way to protect build scripts from accidental version bumps during a release?▼

Build-bump protection prevents accidental version bumps or mutations during release by guarding the build script execution. This defensive pattern stops unauthorized version changes from corrupting the release pipeline artifacts.

Do I need defensive checks for both npm publish workflows and container builds?▼

Yes, defensive checks apply across both npm publish workflows and container builds. Applying semver validation, token governance, and propagation retry ensures verifiable artifacts are safely published regardless of the release pipeline format.

Related Skills

Explore More Software Engineering Skills→
snow-jallensnow-jallen

ci-validation-gates

Enforce semver validation, NPM token verification, and draft-release detection in CI/CD pipelines.

Community
Advanced
Leep-GHLeep-GH

ci-validation-gates

Automate CI/CD validation gates for semver, npm tokens, retries, and draft releases.

Community
Advanced
sachinnair90sachinnair90

ci-validation-gates

Validate semver, token types, retries, and draft-release triggers in GitHub Actions publish workflows.

Community
Advanced
jperezdelrealjperezdelreal

ci-validation-gates

Automate semver validation, token checks, and retry handling in CI/CD release pipelines.

Community
Advanced