skills.rest
lbouriez
lbouriezCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ci-validation-gates

Enforce semver validation, token checks, retry logic, and draft-release detection in CI/CD workflows.

Updated Mar 27, 2026
Search Tags:#automation#semver#ci-cd#token-verification#retry-logic#draft-release
One-click install
npx skills add https://github.com/lbouriez/Squad-Templates --skill ci-validation-gates-lbouriez
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci-validation-gates
Source: https://github.com/lbouriez/Squad-Templates/tree/main/Nectari-Devops-Squad/.copilot/skills/ci-validation-gates
Command: npx skills add https://github.com/lbouriez/Squad-Templates --skill ci-validation-gates-lbouriez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CI/CD pipelines often fail due to invalid semver, improper token types, missing retry logic, and undetected draft releases. This skill centralizes defensive patterns to prevent outages and fragile deployments.

Core Features & Use Cases

  • Semver Validation Gate: enforce 3-part semver (or approved prereleases) before publish.
  • NPM Token Verification: require automation tokens, not user tokens with OTP, for publish steps.
  • Retry Logic for Propagation: implement retries to account for eventual consistency in package registries.
  • Draft Release Detection: ensure workflows trigger only on published releases, not drafts.

Quick Start

Apply these defensive CI/CD patterns in your workflows to validate versions, verify tokens, retry propagation, and detect draft releases 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 enforce semver validation in CI/CD pipelines before publishing?▼

Enforce semver validation in CI/CD by applying a validation gate that checks for 3-part semantic versions or approved prereleases before any publish step. This prevents deployments triggered by invalid version tags.

Why does my GitHub Actions workflow trigger on draft releases?▼

GitHub Actions workflows trigger on draft releases when missing draft-release detection allows unpublished events to propagate. Implementing draft release detection guardrails ensures workflows trigger only on published releases.

How do I verify NPM automation tokens instead of user tokens in release automation?▼

Verify NPM automation tokens in release automation by adding a token integrity check that requires automation tokens rather than user tokens with OTP. This ensures CI/CD publish steps authenticate non-interactively without OTP prompts.

Do I need retry logic for package registry propagation in CI/CD workflows?▼

You need retry logic for package registry propagation in CI/CD workflows to account for eventual consistency in package registries. Implementing retries ensures downstream deployment steps succeed after package availability delays.

Can I integrate defensive CI/CD patterns into existing GitHub Actions pipelines?▼

You can integrate these defensive CI/CD patterns into existing GitHub Actions pipelines because the patterns feature modular structure and explicit frontmatter metadata. This allows easily auditable validation gates to drop into current workflows.

Related Skills

Explore More Software Engineering Skills→
edictum-aiedictum-ai
29

release

Automate semantic version bumping, tagging, pushing, and GitHub Release creation.

Official
Intermediate
kjfsmkjfsm
1

release

Enforce pre-release checks before publishing npm packages via changesets.

Community
Intermediate
mpauloskympaulosky

ci-validation-gates

Validate semver, npm tokens, retry logic, and draft releases in CI/CD pipelines.

Community
Advanced
snow-jallensnow-jallen

ci-validation-gates

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

Community
Advanced