メニュー
Execute mcloud environments commands to list, get, create, delete, redeploy, or trigger builds for Cloud environments. Use when managing environment lifecycle, redeploying after variable changes, or starting new builds from source.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | mcloud-environments |
| description | Execute mcloud environments commands to list, get, create, delete, redeploy, or trigger builds for Cloud environments. Use when managing environment lifecycle, redeploying after variable changes, or starting new builds from source. |
| allowed-tools | Bash(mcloud environments*), Bash(mcloud use*), Bash(jq*) |
Execute mcloud environments commands to manage environment lifecycle and deployments.
type via environments get --json before attempting delete in automation.--yes for destructive operations (delete) in non-interactive contexts.redeploy vs trigger-build are not interchangeable — choose the right one based on where the fix is.List all environments in a project.
mcloud environments list --organization <org-id> --project <project-id-or-handle> --json
Options:
-o/--organization <id> — Organization ID (falls back to active context)-p/--project <id-or-handle> — Project ID or handle (falls back to active context)--json — Output as JSONRetrieve a single environment by handle.
mcloud environments get <environment-handle> --organization <org-id> --project <project-id-or-handle> --json
Arguments:
environment — Environment handle (required)Options:
-o/--organization <id>, -p/--project <id-or-handle>, --jsonCreate a new long-lived environment.
mcloud environments create \
--organization <org-id> \
--project <project-id-or-handle> \
--name "Staging" \
--branch develop \
--json
Options:
-o/--organization <id>, -p/--project <id-or-handle>-n/--name <name> — Environment name (required)-b/--branch <branch> — Git branch to track (required)--custom-subdomain <subdomain> — Optional custom subdomain--json — Output as JSONDelete an environment. Cannot delete production environments.
mcloud environments delete <environment-handle> \
--organization <org-id> \
--project <project-id-or-handle> \
--yes
Arguments:
environment — Environment handle (required)Options:
-o/--organization <id>, -p/--project <id-or-handle>-y/--yes — Skip confirmation prompt (required in non-interactive mode)--json — Output as JSONRe-run an existing build for the active deployment. Use when the fix is environment-side (variable change, infra issue) — does NOT start a new build.
mcloud environments redeploy <environment-handle> \
--organization <org-id> \
--project <project-id-or-handle> \
--json
Arguments:
environment — Environment handle (required)Options:
-o/--organization <id>, -p/--project <id-or-handle>, --jsonRequires the environment to have an active deployment. If it doesn't, use
trigger-buildfirst.
Start a new build from the tracked branch. Use when the fix is committed code — creates a new deployment.
mcloud environments trigger-build <environment-handle> \
--organization <org-id> \
--project <project-id-or-handle> \
--json
Arguments:
environment — Environment handle (required)Options:
-o/--organization <id>, -p/--project <id-or-handle>, --json| Command | When to use |
|---|---|
redeploy | Fix is environment-side (variable change, infra config) — reruns existing build |
trigger-build | Fix is in source code on the tracked branch — starts a new build |
# List all environments
mcloud environments list --json
# Get environment details and check type before deleting
mcloud environments get staging --json | jq '{id, name, type, status}'
# Create a new environment tracking the develop branch
mcloud environments create --name "Staging" --branch develop --json
# Delete a non-production environment
mcloud environments delete staging --yes
# Redeploy after a variable change
mcloud environments redeploy production --json
# Trigger a fresh build from source
mcloud environments trigger-build production --json
# Find environment handles by name
mcloud environments list --json \
| jq -r '.[] | select(.name == "Production") | .handle'
# Verify new build started
mcloud deployments list --environment production --limit 5 --json \
| jq '.[] | {id, backend_status, updated_at}'
Execute mcloud authentication and context commands: login, logout, whoami, use, version, and signup. Use when setting up the CLI, switching accounts, verifying auth state, setting the active org/project/environment context, or checking the CLI version.
Execute mcloud deployments commands to list deployments, retrieve deployment details, and fetch build logs. Use when listing deployments, checking deployment status, or reading build output for debugging build failures.
Execute mcloud logs to fetch and stream runtime logs for Cloud environments. Use when reading backend or storefront logs, filtering by time range, searching for errors, or scoping logs to a specific deployment.
Execute mcloud organizations commands to list or get Cloud organizations. Use when discovering organizations, resolving organization IDs by name, or retrieving organization details including members and subscription.
Execute mcloud projects commands to list, get, or delete Cloud projects. Use when discovering projects, resolving project handles by name, or retrieving project details including linked environments.
Execute mcloud variables commands to list and get environment variables for a Cloud environment. Use when inspecting, reading, or exporting environment variables. Never pass --reveal unless the user explicitly requests secret values.