ci-validation-gates Skill

Source

• Creator: microsoft
• Repository: microsoft/frontier-ghcp-rvas
• Skill file: .squad/templates/skills/ci-validation-gates/SKILL.md

What it does

Defensive CI/CD patterns: semver validation, token checks, retry logic, draft detection — earned from v0.8.22

Skill instructions

Context CI workflows must be defensive. These patterns were learned from the v0.8.22 release disaster where invalid semver, wrong token types, missing retry logic, and draft releases caused a multi-hour outage. Both Drucker (CI/CD) and Trejo (Release Manager) carried this knowledge in their charters — now centralized here. Patterns Semver Validation Gate Every publish workflow MUST validate version format before npm publish. 4-part versions (e.g., 0.8.21.4) are NOT valid semver — npm mangles them. yaml - name: Validate semver run: | VERSION="${{ github.event.release.tagname }}" VERSION="${VERSIONv}" if ! npx semver "$VERSION" /dev/null 2&1; then echo "❌ Invalid semver: $VERSION" echo "Only 3-part versions (X.Y.Z) or prerelease (X.Y.Z-tag.N) are valid." exit 1 fi echo "✅ Valid semver: $VERSION" NPM Token Type Verification NPMTOKEN MUST be an Automation token, not a User token with 2FA: - User tokens require OTP — CI can't provide it → EOTP error - Create Automation tokens at npmjs.com →