skills.rest
webmaxru
webmaxruCOMMUNITY
Explore all skills by this author →
Website𝕏@webmaxruGitHub

ci-validation-gates

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

49|6|Updated Aug 24, 2021
Search Tags:#semver#github-actions#ci-cd#retry#token-verification#draft-releases
One-click install
npx skills add https://github.com/webmaxru/bpm-counter --skill ci-validation-gates-webmaxru
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci-validation-gates
Source: https://github.com/webmaxru/bpm-counter/tree/main/.copilot/skills/ci-validation-gates
Command: npx skills add https://github.com/webmaxru/bpm-counter --skill ci-validation-gates-webmaxru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defensive CI/CD patterns help teams prevent outages and release disasters by enforcing checks before publishing.

Core Features & Use Cases

  • Semver validation gate before releases to avoid invalid version formats.
  • NPM token type verification to ensure automation tokens are used in CI workflows.
  • Retry logic to handle eventual consistency after publishing.
  • Draft release detection and build-protective measures to prevent incomplete deployments.

Quick Start

Install and enable these checks in your CI pipeline to guard every release.

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 releases in GitHub Actions?▼

Semver validation checks version format compliance before publishing, while draft release detection blocks incomplete deployments to ensure only finalized, verified versions propagate through your automated release pipeline.

Why does my npm publish workflow fail due to token type verification?▼

npm token type verification fails when CI workflows use non-automation tokens, so you must configure automation-specific tokens in your CI environment to pass validation checks and protect the publishing process.

How do I handle propagation delays after publishing in a CI pipeline?▼

You handle propagation delays by implementing retry logic in your CI pipeline, which polls for eventual consistency after publishing to confirm the release is fully available before completing the workflow.

Can I use defensive CI/CD checks for npm workflows without additional dependencies?▼

Defensive CI/CD patterns apply broadly to general CI systems and npm workflows, but they are most effective in automated release pipelines where post-publish verification and retry logic can handle eventual consistency.

Related Skills

Explore More Software Engineering Skills→
Elevaria-biaElevaria-bia

aiox-devops

Run automated quality gates and control GitHub push, PR, and release operations.

Community
Advanced
HelloWorldSunginHelloWorldSungin
2

deployment-workflow

Execute production deployments with pre-checks, rollback procedures, and post-deployment validation.

Community
Advanced
WayneWalterBerryWayneWalterBerry

ci-validation-gates

Enforce semver validation and token-type checks in GitHub Actions workflows.

Community
Advanced
garochee33garochee33
3

ci-cd-architect

Design automated CI/CD pipelines with GitHub Actions, Docker, and Terraform.

Community
Advanced