opendeploy-context

OpenDeploy Context

Invocation Preflight

If this skill is invoked directly, first run the global CLI version check unless another OpenDeploy skill already did:

npm list -g @opendeploydev/cli --depth=0 --json
npm view @opendeploydev/cli version --json
opendeploy preflight . --json

If global is older than npm latest, hand off to opendeploy-setup. If the user skips the update, continue with the installed global CLI when it supports the needed commands. Do not run separate --version, jq, or raw curl plugin probes after this preamble.

Context prevents duplicate projects/services and lets agents resume work. The CLI keeps it in .opendeploy/project.json (no API keys, no env values). Team workflow: .opendeploy/project.json is shared deployment context and should be commit-friendly. Do not add a blanket .opendeploy/ entry to .gitignore. Ignore only sensitive/debug subpaths such as .opendeploy/attempts/, .opendeploy/deploy-attempts.jsonl, generated credential/env body files, and support evidence that may include logs.

opendeploy context resolve --json       # alias of `context status`; reads .opendeploy/project.json
opendeploy context save \
  --project <project-id> \
  --service <service-id> \
  --deployment <deployment-id> \
  --live-url <url> \
  --json

context save writes:

{
  "project_id": "string",
  "service_id": "string",
  "deployment_id": "string",
  "live_url": "string",
  "saved_at": "ISO-8601"
}

After every successful first deploy, run context save. On redeploy, run context resolve first to avoid duplicate projects create.

URL paste shortcut

If the user pasted a dashboard URL, extract IDs from the URL instead of calling context resolve. URL forms:

https://dashboard.opendeploy.dev/projects/<PROJECT_ID>
https://dashboard.opendeploy.dev/projects/<PROJECT_ID>/services/<SERVICE_ID>
https://dashboard.opendeploy.dev/projects/<PROJECT_ID>/deployments/<DEPLOYMENT_ID>

About this skill

Invocation Preflight

URL paste shortcut