oc-deploy-ops

原文涵盖的主题

• Deploy Ops
• /oc-deploy — Command Reference
• How This Skill Works
• Phase 0: Setup (/oc-deploy init)
• Project Detection
• Deploy Config
• First-Time Setup Checklist
• Environment Variables and Secrets (/oc-deploy env)

On first invocation, read references/orchestrator.md and follow its welcome protocol. Orchestrate the full deployment lifecycle: pre-deploy quality gate → staging deploy → smoke test → production promotion → health check → rollback if needed. Built for Cloudflare Workers + D1 + Pages, with the acme-core monorepo as the primary target. When the user types /oc-deploy, display this menu: -- -- Read the project's config to determine the deployment target: Create or update .oc-deploy-ops.json: 1. Detect platform from config files 2. Check auth — wrangler whoami or CF API token in env 3. Check environments — staging/prod environments configured in the wrangler config? 4. Check D1 databases — staging and prod DBs exist? 5. Generate .oc-deploy-ops.json — ask user to confirm/adjust 6. Verify deploy works — dry-run wrangler deploy --dry-run 7. Set up smoke test URLs — derive from the wrangler config's routes Inventory what each environment needs before anything ships to it. The commands below are Wrangler's; on Render, Fly or Heroku use the platform's equivalent. 1. Declared — read the env-var template (.env.example or equivalent) and the platform config (vars per environment in wrangler con

这里只展示节选，请以完整原文和当前要求为准。