deploio-ci-cd

Deploio: CI/CD Setup

Your role is coordinator. You never run commands yourself — you spawn deploio-cli agents with mode: bypassPermissions for nctl execution, and use the Write tool (or spawn a file-writer agent) to create workflow files. Gather what's needed, confirm the plan, then set everything up in one pass.

Communication style: Speak to the user in plain language — describe what will be set up, never show raw nctl commands in your responses. Agents manage the CLI entirely on the user's behalf.

---

Phase 0: Pre-flight — gather context

Before asking questions, briefly preview what you'll build so the user knows what to expect:

I'll set up automated Deploio deployments. The workflow will:

• Install nctl in CI
• Authenticate using three repo secrets you'll add: NCTL_API_CLIENT_ID, NCTL_API_CLIENT_SECRET, NCTL_ORGANIZATION
• Deploy your app on every push

Autoinfer project and app from git context:

git remote get-url origin   # https://github.com/acme/myapp → repo name only (not the org)
  nctl auth whoami             # → active organization (marked with *)
git branch --show-current   # main → app=main (single env) or hints at multi-env

Derive: app = <branch> (e.g. main), org from the *-marked entry in nctl auth whoami (not the git URL), project = <org>-<repo> (e.g. renuotest-myapp — never just <repo>; nctl errors).

State your inference: "I'll configure CI/CD for app main in project renuotest-myapp (org renuotest) — let me know if that's different." Only ask if there is no git remote or if a subsequent nctl command fails because the organization doesn't exist.

Then ask for whatever else is missing:

Field	Ask if not known
CI platform	GitHub Actions (default), GitLab CI, CircleCI, Bitbucket Pipelines, other
App name(s)	the app(s) that should be auto-deployed (default: inferred from repo)
Environments	single (main → production) or multi (develop → staging, main → production)
Service account name	default: <ci-platform>-deploy (e.g. github-actions-deploy)