dev-cloudflare-pages-ci-setup

Set up Cloudflare Pages deployment with GitHub Actions workflows. Use when: (1) Deploying a static site to Cloudflare Pages, (2) User says 'cloudflare pages', 'deploy to cloudflare', 'cf pages setup', (3) User wants CI/CD workflows for Cloudflare Pages with PR previews, (4) Setting up wrangler deployment pipelines.

Zur Installation springen

Repository: Takazudo/claude-resources
Letzte Quellaktivität: 9. Juli 2026 um 22:15
Erkannte Sprache von SKILL.md: Englisch
Sterne: 11
Forks: 1

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.

npx skills add https://github.com/Takazudo/claude-resources --skill dev-cloudflare-pages-ci-setup

Der Befehl bleibt in einer Zeile. Scrollen Sie horizontal, um ihn vor dem Kopieren vollständig zu prüfen.

Sie bevorzugen eine lokale Kopie? Laden Sie die Dateien herunter, die SkillsMP derzeit vorliegen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

SKILL.md

Quellanweisungen · Schreibgeschützte Vorschau

Zurück zur Suche Zurück zur Installation

codex-2nd

Get a second opinion from OpenAI Codex CLI on a plan or approach. Use when: (1) During planning phase of /x-as-pr or /x-wt-teams to validate the approach, (2) User says 'codex 2nd', 'second opinion', or 'codex opinion', (3) Wanting an alternative perspective before committing to a plan. Sends context and plan to codex, returns feedback. Called automatically by /x-as-pr and /x-wt-teams during planning.

2026-07-29

codex-imagegen

Generate or redesign raster images (PNG mockups, illustrations, photos, UI design polish) from inside Claude Code by driving Codex CLI's built-in $imagegen, billed to ChatGPT-included usage instead of per-image OpenAI API charges. Use whenever the user wants to create/generate an image, make a mockup or illustration, produce a photo, polish or redesign a UI from a screenshot, or get a PNG out of a session — even if they don't mention Codex or "imagegen". This is the preferred image-generation path because Anthropic models cannot generate raster images and this route avoids API billing.

2026-07-29

codex-research

Web research using OpenAI Codex CLI (codex exec). PREFERRED over general web research. Use when: (1) User says 'research', 'codex research', 'look up', or 'investigate', (2) Researching libraries, APIs, best practices, or technical topics, (3) Gathering information from the web. Codex performs research, Claude Code synthesizes. Falls back to Claude Code researcher subagent if codex unresponsive.

2026-07-29

Alle aus diesem Repository ansehen

name	dev-cloudflare-pages-ci-setup
description	Set up Cloudflare Pages deployment with GitHub Actions workflows. Use when: (1) Deploying a static site to Cloudflare Pages, (2) User says 'cloudflare pages', 'deploy to cloudflare', 'cf pages setup', (3) User wants CI/CD workflows for Cloudflare Pages with PR previews, (4) Setting up wrangler deployment pipelines.

Cloudflare Pages CI Setup

Set up Cloudflare Pages deployment with GitHub Actions workflows for static sites. Supports production deploys, PR preview deploys, and named preview branches.

Step 1: Gather Project Info

Identify the project's build setup:

cat package.json
ls .github/workflows/ 2>/dev/null
cat wrangler.toml 2>/dev/null

Determine: package manager (pnpm/npm/yarn), build command, output directory (dist/, build/, out/), base path (root / or subpath like /pj/project-name/).

Step 2: Ask User Preferences

Cloudflare Pages project name (used in --project-name)
Which workflows: Main only, Main + PR previews, Main + PR + named previews
Base path: root / or specific subpath
IFTTT notifications: yes/no

Step 3: Create Cloudflare Configuration

wrangler.toml

# Cloudflare Pages project configuration

compatibility_date = "2024-12-01"

Add wrangler devDependency

pnpm add -D wrangler

permissions: contents: read jobs: build: # Heavy job — candidate for a larger cloud runner; see /dev-blacksmith-migration runs-on: ubuntu-latest timeout-minutes: 15 steps: # fetch-depth: 0 if project needs git history (e.g., doc history, changelogs) - uses: actions/checkout@v4 - uses: pnpm/action-setup@v4 - uses: actions/setup-node@v4 with: { node-version: 20 } - run: pnpm install --frozen-lockfile - run: pnpm build - uses: actions/upload-artifact@v4 with: { name: dist-out, path: dist/, retention-days: 1 } deploy: needs: build runs-on: ubuntu-latest timeout-minutes: 20 steps: - uses: actions/download-artifact@v4 with: { name: dist-out, path: deploy/ } - run: npm install -g wrangler@4 - name: Deploy to Cloudflare Pages (production) run: | for attempt in 1 2 3; do echo "Deploy attempt $attempt/3..." if wrangler pages deploy deploy \ --project-name=PROJECT_NAME \ --branch=main \ --commit-hash="${GITHUB_SHA}" \ --commit-message="Production deploy: ${GITHUB_SHA}"; then echo "Deploy succeeded on attempt $attempt" exit 0 fi if [ "$attempt" -lt 3 ]; then echo "Deploy failed, retrying in 150 seconds..." sleep 150 fi done echo "Deploy failed after 3 attempts" exit 1 env: CLOUDFLARE_API_TOKEN: ${{ secrets.CLOUDFLARE_API_TOKEN }} CLOUDFLARE_ACCOUNT_ID: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }} notify: # Optional IFTTT notification needs: [build, deploy] if: always() runs-on: ubuntu-latest timeout-minutes: 5 steps: - name: Notify via IFTTT if: env.IFTTT_PROD_NOTIFY != '' env: IFTTT_PROD_NOTIFY: ${{ secrets.IFTTT_PROD_NOTIFY }} BUILD_RESULT: ${{ needs.build.result }} DEPLOY_RESULT: ${{ needs.deploy.result }} SERVER_URL: ${{ github.server_url }} REPO: ${{ github.repository }} RUN_ID: ${{ github.run_id }} run: | if [ "$DEPLOY_RESULT" = "success" ]; then STATUS="✅ succeeded" elif [ "$BUILD_RESULT" = "failure" ]; then STATUS="❌ failed (build)" elif [ "$DEPLOY_RESULT" = "failure" ]; then STATUS="❌ failed (deploy)" else STATUS="⚠️ cancelled"; fi RUN_URL="${SERVER_URL}/${REPO}/actions/runs/${RUN_ID}" curl -sSf --max-time 10 -X POST "$IFTTT_PROD_NOTIFY" \ -H 'Content-Type: application/json' \ -d "{ \"value1\": \"PROJECT_NAME: ${STATUS}\", \"value2\": \"${RUN_URL}\", \"value3\": \"\" }" || echo "::warning::IFTTT notification failed"

Field	Content	Example
`value1`	`<project>: <emoji> <status>`	`my-app: ✅ Deploy succeeded`
`value2`	Run URL for tapping through	`https://github.com/.../runs/123`
`value3`	(unused / empty)	`""`

Secret	Required	Purpose
`CLOUDFLARE_API_TOKEN`	Yes	Wrangler authentication
`CLOUDFLARE_ACCOUNT_ID`	Yes	Cloudflare account identifier
`IFTTT_PROD_NOTIFY`	No	IFTTT webhook URL (skipped if not set)

dev-cloudflare-pages-ci-setup

Installationsoptionen

Quelldateien prüfen

Cloudflare Pages CI Setup

Step 1: Gather Project Info

Step 2: Ask User Preferences

Step 3: Create Cloudflare Configuration

wrangler.toml

Add wrangler devDependency

Cloudflare Pages CI Setup

Step 1: Gather Project Info

Step 2: Ask User Preferences

Step 3: Create Cloudflare Configuration

wrangler.toml

Add wrangler devDependency

public/_redirects (if using a base path)

Step 4: Create Workflows

Security Best Practices (apply to all workflows)

Deploy Retry (apply to all deploy steps)

Production Deploy (main-deploy.yml)

PR Preview Deploy (pr-checks.yml)

Named Preview Deploy (preview-deploy.yml)

Step 5: Required Secrets

Creating Cloudflare API Token

Step 6: Verify

Companion Skills

dev-cloudflare-pages-ci-setup

Quellinformationen

Installationsoptionen

Quelldateien prüfen

Mehr aus diesem Repository

Cloudflare Pages CI Setup

Step 1: Gather Project Info

Step 2: Ask User Preferences

Step 3: Create Cloudflare Configuration

wrangler.toml

Add wrangler devDependency

Cloudflare Pages CI Setup

Step 1: Gather Project Info

Step 2: Ask User Preferences

Step 3: Create Cloudflare Configuration

wrangler.toml

Add wrangler devDependency

public/_redirects (if using a base path)

Step 4: Create Workflows

Security Best Practices (apply to all workflows)

Deploy Retry (apply to all deploy steps)

Production Deploy (main-deploy.yml)

PR Preview Deploy (pr-checks.yml)

Named Preview Deploy (preview-deploy.yml)

Step 5: Required Secrets

Creating Cloudflare API Token

Step 6: Verify

Companion Skills

Mehr aus diesem Repository