C.R.A.B Deploy Agent

**Quick judgement** A mature, opinionated deployment helper best suited for JavaScript/Next.js full-stack apps targeting GitHub + Cloudflare Pages, with strong guardrails via explicit human approvals at each step. It provides a clear, stateful workflow but is intentionally narrow in platform support and relies heavily on external CLI tools and correct environment setup. **What it does well** - Orchestrates a full deployment lifecycle: `init → build → test → push → deploy`, plus `status`, `continue`, `cancel`, and `list` for operational control. - Enforces human approval at each major stage, reducing accidental pushes or mis-deployments and making it safer in small-team environments. - Persists deployment state in local JSON, enabling resumable workflows and visibility into each deployment’s current step and outcome. - Offers concrete, implementation-level guidance for Next.js + Cloudflare D1 (dependencies, `wrangler.toml`, edge runtime, D1 bindings, build settings, and common error fixes). - Integrates cleanly with standard tools (`git`, `gh`, `wrangler`, `jq`) instead of reinventing VCS or hosting logic. **Key risks & limitations** - **Platform opinionated**: Strongly oriented toward GitHub + Cloudflare Pages (and especially Next.js + D1). Other stacks or providers are not first-class and may require manual adaptation. - **External tooling dependency**: Reliability and user experience depend on correct installation and configuration of `gh`, `wrangler`, `git`, `jq`, Cloudflare tokens, and Node/npm. Misconfiguration will surface as tool errors outside the skill’s direct control. - **Limited advanced deployment features**: No explicit mention of rollbacks, multi-environment promotion (dev/stage/prod), blue-green/canary deployments, or automated test gating beyond manual approval. - **Local state management**: State stored under `~/.clawdbot/skills/deploy-agent/state/` is simple and transparent, but can be corrupted or lost if users manually edit/delete files or switch machines without syncing. - **Security considerations**: Requires handling of GitHub and Cloudflare credentials/token configs; mismanagement of these outside the skill could lead to pushing code to the wrong repo or deploying to unintended domains. **Recommended scenarios** - You are building a Next.js or JS-based full-stack app and want a guided, semi-automated path from local dev to GitHub and Cloudflare Pages. - You value **manual approval gates** for each deployment phase rather than fully automated CI/CD, e.g., for small teams, staging-like workflows, or cautious production releases. - You want a repeatable, documented deployment routine and concrete recipes for common Cloudflare + D1 pitfalls. **Less ideal if** - You need provider-agnostic deployment (AWS, GCP, custom Kubernetes, etc.) or support for non-JS stacks as first-class citizens. - You require advanced continuous delivery features (automatic promotion, complex branching strategies, rollbacks) integrated into the tooling itself. - Your environment cannot easily support the required CLIs and token configuration, or you prefer a fully hosted CI/CD solution over a local, stateful CLI-based workflow.