cloudflare-ci-cd-github-actions

Automate GitHub Actions CI/CD pipelines for Cloudflare Workers and Pages.

2|Updated Dec 5, 2025

Search Tags:#automation #ci/cd #deployment #migrations #github actions #cloudflare #workers

Ready to run

npx skills add https://github.com/AgentiveCity/SkillFactory --skill cloudflare-ci-cd-github-actions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cloudflare-ci-cd-github-actions
Source: https://github.com/AgentiveCity/SkillFactory/tree/main/.claude/skills/cloudflare-ci-cd-github-actions
Command: npx skills add https://github.com/AgentiveCity/SkillFactory --skill cloudflare-ci-cd-github-actions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Setting up, refactoring, or maintaining a GitHub Actions CI/CD pipeline for deploying Cloudflare Workers/Pages apps with D1/R2, including tests, builds, migrations, and multi-environment deploys, can be complex and time-consuming. This Skill automates the creation of fast, reliable, and readable pipelines, reducing manual effort and deployment errors.

Core Features & Use Cases

Comprehensive CI/CD Workflows: Create GitHub Actions workflows for testing, linting, building, and deploying Workers/Pages apps on push or pull request.
Multi-Environment Deployment: Automate deployments to dev, staging, and production environments, including D1 migrations and environment-specific API tokens.
Secure Secrets & Preview Deploys: Wire Cloudflare API tokens securely into GitHub Actions and support optional preview deployments for feature branches.

Quick Start

Create CI + deploy GitHub Actions for my Hono Worker on Cloudflare, running tests and deploying to staging on every push to develop, and deploying to production only on main with D1 migrations included.

Frequently Asked Questions about cloudflare-ci-cd-github-actions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate Cloudflare Workers deployments with GitHub Actions?▼

Automate Cloudflare Workers deployments by creating GitHub Actions workflows that handle testing, building, and deploying to multiple environments. This Skill generates baseline ci.yml and deploy.yml workflows configured for your Workers/Pages setup, managing secrets securely and supporting D1 migrations across dev, staging, and production.

Can I run D1 migrations automatically in my GitHub Actions CI/CD pipeline?▼

Yes, this Skill automates D1 migrations via Wrangler within your GitHub Actions workflows, enforcing safe migration ordering and environment-specific execution. It integrates migrations into multi-environment deployments so schema changes apply correctly before code deploys to each target environment.

How do I set up preview deployments for Cloudflare Workers on feature branches?▼

GitHub Actions workflows generated by this Skill support optional preview deployments for feature branches, wiring Cloudflare API tokens securely and triggering deploys on pull requests. Configure the workflow to deploy preview URLs alongside your dev, staging, and production environments.

What's the best way to manage Cloudflare API tokens securely in GitHub Actions?▼

This Skill handles token and secret wiring by integrating Cloudflare API credentials into GitHub Actions as encrypted secrets, ensuring tokens are never exposed in logs or workflows. It applies environment-specific tokens for dev, staging, and production so each deployment uses the correct authentication context.

Can I use GitHub Actions to test and lint my Cloudflare Workers before deployment?▼

Yes, this Skill creates comprehensive CI workflows including testing and linting steps that run on push and pull request events. The generated ci.yml runs your test suite and linters before any deployment workflow executes, catching errors early in the pipeline.

Do I need to manually configure separate workflows for development, staging, and production?▼

No, this Skill generates reusable workflows that automate multi-environment deployment logic. A single deploy.yml handles routing to dev, staging, and production based on the Git branch, eliminating manual workflow duplication across environments.