What problem does it solve?
This Skill centralizes defensive CI/CD patterns to prevent release outages caused by invalid semver, wrong token types, missing retry logic, draft releases, and accidental version mutation observed in real incidents.
Core Features & Use Cases
- Semver Validation Gate: Ensures publish workflows validate tag format and reject non-semver or 4-part versions before npm publish.
- Token Type Verification: Verifies NPM_TOKEN is an Automation token (not a user token requiring 2FA) to avoid EOTP failures.
- Retry & Verification Logic: Implements retry-based checks for npm registry propagation and explicit verification attempts after publish.
- Draft Detection & Build Protection: Detects draft releases, enforces publish-on-published events, and requires SKIP_BUILD_BUMP to prevent build-time version mutation.
- Use Case: Harden a Node package release pipeline to avoid multi-hour outages caused by malformed versions, wrong token usage, or eventual consistency timing issues.
Quick Start
Run the ci-validation-gates checklist against my repository to validate semver, confirm npm automation token usage, verify registry propagation with retries, and ensure the release is published before proceeding.