ccc-deploylisted

# /ccc-deploy — Actual Deploy Workflow **CC Commander** · /ccc-deploy · Detect target → deploy → verify → announce Use this when the user is ready to push a build live. This is distinct from `/ccc-ship` and `/ccc-deploy-check`: `/ccc-ship` handles pre-flight and release tagging, `/ccc-deploy-check` is a readiness gate, and `/ccc-deploy` runs the real deploy. ## Response Shape Always return these sections: 1. Brand header: ```markdown **CC Commander** · /ccc-deploy · Actual deployment ``` 2. Detection summary: Read the repository root and report detected deploy targets from: - `package.json` scripts: `deploy`, `deploy:prod`, `deploy:production`, `pages:deploy`, `wrangler:deploy`, `vercel:deploy`, `fly:deploy`, `publish`, `release` - `fly.toml` → Fly.io - `vercel.json` or a `vercel` package/script → Vercel - `wrangler.toml`, `wrangler.json`, or `wrangler.jsonc` → Cloudflare - `.github/workflows/deploy.yml`, `.github/workflows/deploy.yaml`, `.github/workflows/pages.yml`, or `.github/workflows/pages.yaml` → GitHub Pages or workflow deploy - `package.json` `publishConfig`, `bin`, or `files` plus a `prepublishOnly` script → npm package publish candidate Use parallel Bash reads where possible and keep failures non-fatal: ```bash test -f package.json && node -e "const p=require('./package.json'); console.log(JSON.stringify({scripts:p.scripts||{}, publishConfig:p.publishConfig||null, bin:p.bin||null, files:p.files||null}, null, 2))" test -f fly.toml && echo fly.toml test -f