skills.rest
acmeleme
acmelemeOFFICIAL
Explore all skills by this author →
GitHub

ci-validation-gates

Apply defensive gating checks to CI/CD publish workflows for semver, tokens, and retries.

Updated Nov 11, 2025
Search Tags:#semver#ci-cd#token-verification#defensive-patterns#retry-logic#draft-release#release-pipelines
One-click install
npx skills add https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator --skill ci-validation-gates-acmeleme
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci-validation-gates
Source: https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator/tree/main/.squad/templates/skills/ci-validation-gates
Command: npx skills add https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator --skill ci-validation-gates-acmeleme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defensive CI/CD patterns to catch misconfigurations early and enforce safe release practices, reducing outages and hotfixes.

Core Features & Use Cases

  • Semver validation gate to prevent invalid and malformed versions from being published.
  • NPM token type verification to ensure automation tokens are used for CI tasks instead of user tokens.
  • Retry logic for npm registry propagation to handle eventual consistency after publish.
  • Draft release detection to ensure workflows trigger only on released versions, not drafts.
  • Build script protection to guard against accidental version bumps or unsafe build mutations.

Quick Start

Add the provided checks to your CI workflow to validate semver, verify automation tokens, and retry package propagation.

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 tags from triggering a release pipeline?▼

Prevent invalid semver tags from triggering a release pipeline by adding a semver validation gate to your CI workflow, catching malformed versions before they reach the publish step.

How do I verify automation tokens are used instead of user tokens in npm publish workflows?▼

Verify npm automation tokens instead of user tokens in publish workflows by implementing token type verification checks, ensuring CI tasks use the correct authentication credentials.

Why does my npm package publish succeed but fail registry propagation in CI?▼

Registry propagation fails after a successful npm package publish in CI due to eventual consistency, which you can resolve by adding retry logic to your release pipeline.

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

Stop GitHub Actions workflows from running on draft releases by adding draft release detection checks, ensuring your pipelines trigger only on fully released versions.

Can I apply defensive CI/CD patterns to existing YAML release pipelines without dependencies?▼

You can apply defensive CI/CD patterns to existing YAML release pipelines without external dependencies by directly defining gating checks, retry strategies, and safety constraints in your workflow files.

Related Skills

Explore More Software Engineering Skills→
elbrunoelbruno
2

ci-validation-gates

Enforce CI/CD gates validating semver, NPM_TOKEN, and release events.

Community
Advanced
webmaxruwebmaxru
49

ci-validation-gates

Enforce semver validation, token verification, and retry logic in CI/CD release pipelines.

Community
Advanced
olivomarcoolivomarco
66

ci-validation-gates

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

Community
Advanced
snow-jallensnow-jallen

ci-validation-gates

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

Community
Advanced