ci-validation-gates

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

7|Updated Oct 24, 2020
One-click install
npx skills add https://github.com/snow-jallen/HomeSpeaker --skill ci-validation-gates-snow-jallen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-validation-gates
Source: https://github.com/snow-jallen/HomeSpeaker/tree/main/.copilot/skills/ci-validation-gates
Command: npx skills add https://github.com/snow-jallen/HomeSpeaker --skill ci-validation-gates-snow-jallen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The CI/CD process often fails due to insufficient validation, insecure tokens, missing retry logic, and unhandled draft releases. This Skill provides a defensive pattern library to harden release workflows.

Core Features & Use Cases

  • Semver validation gate to prevent invalid version formats from being published.
  • NPM token type verification to ensure automation tokens are used for CI tasks.
  • Retry logic for npm registry propagation to handle eventual consistency after publish.
  • Draft release detection and handling to ensure workflows respond only to published releases.
  • Build-bump protection to avoid unintended version mutations during release.

Quick Start

Integrate this pattern into your CI workflow to validate versions, verify automation tokens, and retry after publish.

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 format in a CI/CD pipeline before publishing?

To validate semver in a CI/CD pipeline, use a semver validation gate to catch invalid version formats before release. This defensive pattern prevents malformed version tags from breaking automated release workflows.

How do I verify npm automation tokens for CI tasks?

Verifying npm automation tokens for CI tasks requires an NPM token type verification step. This ensures automation tokens are strictly used for CI workflows rather than manual publish tokens.

How do I handle npm registry propagation delays in release pipelines?

Handling npm registry propagation delays in release pipelines requires implementing retry logic after publish. This accounts for eventual consistency, ensuring downstream release steps wait for registry updates.

How to prevent GitHub Actions workflows from triggering on draft releases?

To prevent workflows from triggering on draft releases, implement draft-release detection checks. This ensures automated release workflows respond only to published releases, ignoring drafts entirely.

What is the best way to avoid unintended version mutations during a release?

The best way to avoid unintended version mutations during a release is to use a build-bump safeguard flag. This protection mechanism prevents accidental version changes from slipping through automated workflows.

Does this defensive CI/CD validation pattern work without external dependencies?

This defensive CI/CD validation pattern works without external dependencies. It provides a pattern library to harden release workflows directly within your existing automated CI pipelines.