← ClaudeAtlas

ship-sitelisted

Publish a static site or Vite/React app to Cloudflare Pages and prove it is live. Use when the user says ship, publish, deploy, push live, release, or "put it on the site"; when a Pages secret was set or changed and must take effect; when a file is too big for Pages; or when a Pages Function (a contact form, an API route) fails on the live site.
skyeyesec333/ship-site · ★ 0 · API & Backend · score 72
Install: claude install-skill skyeyesec333/ship-site
# Ship a site to Cloudflare Pages A release flow refined over dozens of releases of a production site: a large three.js app with a Pages Function behind its contact form and its big media on R2. ``` 1. look git status; decide what ships and what does not 2. commit plain message saying what visitors will see; noreply author; push 3. build the project's build command into the output folder; size check 4. deploy wrangler pages deploy <out> --project-name <p> --branch <b> 5. check scripts/check-live.mjs against every live address ``` `scripts/` means the `scripts/` folder **in this skill's own directory** (`${CLAUDE_SKILL_DIR}/scripts/`, for a plugin or a copied skill alike), not the user's project. Run the scripts by that full path from the project root. Do every step every time, and report what the live check printed. "Deployed" without step 5 is not shipped. ## Config Read `ship.config.json` at the project root if it exists; otherwise ask once and offer to write it: ```json { "project": "my-site", "branch": "main", "build": "npm run build", "out": "dist", "live": ["https://example.com", "https://www.example.com", "https://my-site.pages.dev"] } ``` `project` is the Cloudflare Pages project name, `branch` the one Pages treats as production. A `wrangler.toml` with `pages_build_output_dir` gives `out` too. ## 1. Look before shipping - `git status --short` and `git diff --stat`. A dirty tree is normal: other work may be half done. **Ship only