cloudflare-commerce-deploy

Deploy and operate commerce apps on Cloudflare when a user wants Pages or Workers deployment, DNS/custom domains, storage bindings, secrets, logs, per-environment env vars, or optional Registrar domain registration handled by an agent.

cloudflarepagesdns house

install · efd09da

# CLI (primary)

$ autovault add jack-arturo/skillissue@efd09da503770bce1de134fc485f62e65f1d38c3:skills/cloudflare-commerce-deploy/SKILL.md --sync-profiles

# MCP tool call

add_skill({ source: "github", identifier: "jack-arturo/skillissue@efd09da503770bce1de134fc485f62e65f1d38c3:skills/cloudflare-commerce-deploy/SKILL.md" })

→ vault validates · signs · syncs agent skill dirs

source: jack-arturo/skillissue

Why it exists

Commerce launches need DNS, secrets, and preview/prod isolation — not ad-hoc wrangler folklore.

History

1.0.3

Git-connected Pages order of operations codified; preview env var PATCH documented.

How Jack actually uses it

Use for domain attach and deploy model selection. Billable registrar actions still need confirmation.

What it is not

Not a generic tutorial. It's the house runbook for this machine and these agents.

cloudflare-ops

Package

Version 1.0.3 · install pin efd09da · SSOT skills/cloudflare-commerce-deploy/ on GitHub · agents: claude-code, codex, autojack