ci-validation-gates

You can enforce semantic versioning validation by running this skill to check version formats against defense patterns before publishing. This prevents npm issues and safeguards build scripts against version mutations during the release process.

Deployment workflows fail on draft releases when draft detection is not enforced. This skill prevents workflows from executing on draft releases only, ensuring pipelines only trigger on finalized, valid release tags for fault-tolerant deployment workflows.

To verify automation token types for npm publish, this skill validates that automation tokens are used to avoid security breaches. It checks your CI/CD pipeline configuration to enforce token verification and maintain pipeline reliability.

The best way to add retry logic to deployment scripts is to implement fallback mechanisms that ensure registry consistency after npm publish. This skill validates that your CI/CD pipeline includes these retry mechanisms to achieve fault-tolerant, versioned release workflows.

Yes, these CI/CD validation gates are applicable to continuous integration and deployment systems aiming for fault-tolerant, versioned release workflows. The skill validates your pipeline configuration against known defense patterns without requiring specific dependencies.

A CI/CD pipeline should have security checks for semantic versioning validation, automation token verification, and draft release detection. This skill enforces these defensive patterns to prevent common issues, security breaches, and outages during npm publishing.