skills.rest
jperezdelreal
jperezdelrealCOMMUNITY
Explore all skills by this author →
GitHub

ci-validation-gates

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

Updated Apr 6, 2026
Search Tags:#automation#workflow#security#semver#retry#ci#cd
One-click install
npx skills add https://github.com/jperezdelreal/GymBro --skill ci-validation-gates-jperezdelreal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci-validation-gates
Source: https://github.com/jperezdelreal/GymBro/tree/main/.copilot/skills/ci-validation-gates
Command: npx skills add https://github.com/jperezdelreal/GymBro --skill ci-validation-gates-jperezdelreal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates defensive CI/CD governance to prevent faulty releases and outages.

Core Features & Use Cases

  • Semver validation before publish to ensure only valid versions are released.
  • NPM token type verification to require Automation tokens for CI workflows.
  • Retry propagation handling to accommodate eventual consistency after publish.
  • Draft-release detection to avoid triggering workflows from drafts.
  • Build protection and gating to disable unintended bumps during releases.

Quick Start

Add the semver validation gate, token verification, and retry propagation steps to your release workflow and validate on 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 automate defensive CI/CD gates to prevent faulty npm releases?▼

Automate defensive CI/CD gates by adding semver validation, automated token checks, and retry propagation handling to your release workflows. This prevents faulty npm releases by verifying versions and tokens before publishing.

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

GitHub Actions workflows trigger from drafts when draft-release detection is missing. Implementing draft-release detection gates prevents workflows from accidentally triggering on incomplete drafts.

How do I verify NPM automation tokens for CI workflows?▼

Verify NPM automation tokens by implementing token type verification gates in your CI workflows. This ensures only Automation tokens are used for CI workflows, preventing unauthorized artifact publishing.

What is retry propagation handling in CI/CD pipelines?▼

Retry propagation handling in CI/CD pipelines accommodates eventual consistency after artifact publishing. It ensures release workflows manage delays between npm package availability and downstream validation steps.

Does this CI validation work with GitHub Actions and npm publishing?▼

Yes, this CI validation works with GitHub Actions and npm publishing. It applies defensive release gates, semver validation, and token verification across npm, GitHub Actions, and similar CI environments.

How do I validate semver before publishing an npm package?▼

Validate semver before publishing an npm package by adding a semver validation gate to your release pipeline. This ensures only valid version numbers are released, preventing unintended version bumps during builds.

Related Skills

Explore More Software Engineering Skills→
mpauloskympaulosky

ci-validation-gates

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

Community
Advanced
PlagueHOPlagueHO
2

ci-validation-gates

Enforce semver, token-type, retry, and draft-release checks in GitHub Actions workflows.

Community
Advanced
sachinnair90sachinnair90

ci-validation-gates

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

Community
Advanced
paleoterrapaleoterra
2

ci-cd-helper

Generate GitHub Actions workflows and Fastlane configurations for macOS apps.

Community
Intermediate