cloudflare-workers-ci-cd

Configure production-ready deployment pipelines for Cloudflare Workers using GitHub Actions or GitLab CI. This skill covers automated testing on every commit, multi-environment deployments, preview URLs per pull request, secrets management, and deployment verification to prevent failures and enforce safe release practices.

Cloudflare Workers CI/CD sets up automated testing and deployment pipelines for Workers via GitHub Actions or GitLab CI.

AI-generated summary based on this skill's SKILL.md

★ 196 ⁮ 29 MIT updated 2026-07-25 by secondsky

Install

secondsky/claude-skills/cloudflare-workers-ci-cd · repository language: TypeScript

Manual (git clone) CLI (skillfed)

git clone https://github.com/secondsky/claude-skills
cp -r claude-skills/plugins/cloudflare-workers/skills/cloudflare-workers-ci-cd ~/.claude/skills/cloudflare-workers-ci-cd

npx skillfed install secondsky/claude-skills/cloudflare-workers-ci-cd

Frequently asked questions

AI-generated answers based on this skill's SKILL.md and metadata

How do I set up CI/CD for Cloudflare Workers?

cloudflare-workers-ci-cd enables you to configure production-ready deployment pipelines using GitHub Actions or GitLab CI. Start by creating a workflow file that triggers on push or pull request events, authenticate with your Cloudflare API token stored as a secret, and use wrangler commands to deploy. The skill guides you through multi-environment setups (staging, production, preview) with automated testing on every commit and preview URLs generated per pull request.

What's the best way to manage secrets in Cloudflare Workers deployments?

cloudflare-workers-ci-cd teaches secure secrets management by storing your Cloudflare API token and environment-specific variables as encrypted secrets in GitHub or GitLab. Never commit sensitive data to your repository. Instead, reference secrets in your workflow using GitHub's ${{ secrets.CLOUDFLARE_API_TOKEN }} syntax or GitLab's $CI_JOB_TOKEN, and pass them to wrangler deploy commands. This prevents credential exposure while maintaining secure multi-environment deployments.

Can cloudflare-workers-ci-cd help with blue-green and canary deployments?

Yes. cloudflare-workers-ci-cd covers advanced deployment strategies including blue-green deployments (running two identical environments and switching traffic) and canary deployments (gradually rolling out changes to a subset of users). The skill also includes rollback strategies to quickly revert failed deployments. These patterns ensure safe release practices and minimize downtime when deploying critical Workers.

How do I deploy Cloudflare Workers to multiple environments automatically?

cloudflare-workers-ci-cd shows how to configure your GitHub Actions or GitLab CI pipeline to deploy to staging, production, and preview environments based on branch or event triggers. Use conditional steps in your workflow to target different environments, manage environment-specific secrets separately, and leverage wrangler's environment configuration to deploy the same code with different bindings and variables to each target.

What should I do when my Cloudflare Workers GitHub Actions deployment fails?

cloudflare-workers-ci-cd provides troubleshooting guidance for common CI/CD failures. Check that your Cloudflare API token is correctly stored as a secret and hasn't expired, verify wrangler is properly installed and configured, review workflow logs for authentication or build errors, and ensure your wrangler.toml matches your deployment target. The skill covers deployment verification steps to catch issues before they reach production.

How can I generate preview URLs for pull requests with Cloudflare Workers?

cloudflare-workers-ci-cd teaches you to configure your GitHub Actions workflow to automatically deploy preview versions of your Workers on pull request events. Each PR gets a unique preview URL, allowing reviewers to test changes before merging. Use wrangler's preview deployment features and comment the preview URL back to the PR, enabling safe review and validation workflows before production release.

SKILL.md

rendered from the published skill — quoted content, verbatim