deploy-cloudflare-bindings

Synchronize Cloudflare Worker bindings and wrangler configuration in CI/CD pipelines.

1|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/jdconley/wodbrains --skill deploy-cloudflare-bindings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-cloudflare-bindings
Source: https://github.com/jdconley/wodbrains/tree/main/.cursor/skills/deploy-cloudflare-bindings
Command: npx skills add https://github.com/jdconley/wodbrains --skill deploy-cloudflare-bindings

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures your Continuous Integration and Deployment pipelines correctly handle changes to Cloudflare Worker bindings (like R2, D1, DO, assets) and wrangler configuration, preventing deployment failures.

Core Features & Use Cases

  • CI/CD Synchronization: Updates GitHub Actions workflows to include new environment variables and secrets required by Cloudflare Workers.
  • Configuration Generation: Manages the automatic generation of wrangler.jsonc based on environment variables.
  • Use Case: After adding a new R2 bucket binding to your Cloudflare Worker, this Skill helps you update your CI to recognize the new binding, create the necessary Cloudflare resource, and deploy the updated worker.

Quick Start

Update the CI configuration to include the new CLOUDFLARE_R2_BUCKET_OG_IMAGES environment variable.

Frequently Asked Questions about deploy-cloudflare-bindings

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

FAQPage Schema
How do I update GitHub Actions secrets when adding new Cloudflare Worker bindings?

When your Cloudflare Worker deployment fails after adding bindings, it is usually because the CI/CD pipeline lacks the necessary GitHub Actions secrets or environment variables required by the updated wrangler configuration.

How do I automate wrangler.jsonc generation from environment variables in CI/CD?

You can automate wrangler.jsonc generation by running a configuration generator script within your GitHub Actions workflow that maps your defined environment variables to the corresponding Cloudflare Worker bindings.

Why does my Cloudflare Worker deployment fail after adding an R2 bucket binding?

Your Cloudflare Worker deployment fails because the CI/CD pipeline is not synchronized with the new bindings, requiring updates to GitHub Actions secrets, environment variables, and the wrangler configuration generator script to recognize the R2 bucket.

Can I use this to synchronize D1 database bindings in my GitHub Actions workflow?

Yes, you can use this to synchronize D1 database bindings by updating your GitHub Actions workflow to include the necessary environment variables and modifying the wrangler configuration to properly map the D1 resources.

What is the best way to manage Cloudflare environment variables across multiple deployment environments?

The best way to manage Cloudflare environment variables is to use a CI/CD synchronization approach that automatically updates GitHub Actions secrets and regenerates the wrangler configuration based on the target deployment environment.