medusajs/medusa-agent-skills

mcloud-deployments

Execute mcloud deployments commands to list deployments, retrieve deployment details, and fetch build logs.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/medusajs/medusa-agent-skills --skill mcloud-deployments

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Cloud CLI: Deployments Commands

Execute mcloud deployments commands to inspect deployments and their build logs.

Constraints

  • Always pass --json when parsing output — plaintext format may change.
  • Always confirm context (mcloud whoami --json) before running commands if org/project are not already known.
  • Use --deployment IDs in the format depl_* or build IDs; build IDs resolve to their latest deployment automatically.

Commands

deployments list

List recent deployments for a project (default: 20 most recent across all environments).

bash
mcloud deployments 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)
  • -e/--environment <handle> — Filter by environment handle
  • --environment-type <production|long-lived|preview> — Filter by environment type
  • --commit <sha> — Filter by Git commit SHA (full or prefix)
  • --limit <1-200> — Max results (default: 20)
  • --offset <number> — Pagination offset (default: 0)
  • --json — Output as JSON

deployments get

Retrieve a single deployment's details by ID.

bash
mcloud deployments get <deployment-id> --organization <org-id> --project <project-id-or-handle> --json

Arguments:

  • deployment — Deployment ID (required)

Options:

  • -o/--organization <id>, -p/--project <id-or-handle>, --json

deployments build-logs

Fetch build logs for a deployment. Use this to debug build-failed status.

bash
mcloud deployments build-logs <deployment-id> --organization <org-id> --project <project-id-or-handle>

Arguments:

  • deployment — Deployment ID (required)

Options:

  • -o/--organization <id>, -p/--project <id-or-handle>
  • --type <backend|storefront> — Which build log stream to read (default: backend)
  • --json — Output as JSON

Deployment Statuses

StatusMeaning
createdBuild not started yet
buildingBuild running
builtBuild succeeded, awaiting rollout
deployingRolling out to environment
deployedLive and serving traffic
build-failedBuild step failed — read build-logs
deployment-failedBuild succeeded, runtime crashed — read mcloud logs
timed-outExceeded time budget (backend only)
canceledSuperseded by a newer deployment
idleNo longer the active deployment

Examples

bash
# List all deployments (with active context set)
mcloud deployments list --json

# Find most recent build-failed deployment
mcloud deployments list --json \
  | jq -r '[.[] | select(.backend_status == "build-failed")][0].id'

# Get deployment details
mcloud deployments get bld_01ABC123 --json

# Read backend build logs
mcloud deployments build-logs bld_01ABC123

# Read storefront build logs
mcloud deployments build-logs bld_01ABC123 --type storefront

# Filter deployments by commit SHA
mcloud deployments list --commit a1b2c3d --json | jq '.'

# Get deployments for a specific environment
mcloud deployments list --environment production --json

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
medusajs
公式

building-admin-dashboard-customizations

Load automatically when planning, researching, or implementing Medusa Admin dashboard UI (widgets, custom pages, forms, tables, data loading, navigation). REQUIRED for all admin UI work in ALL modes (planning, implementation, exploration). Contains design patterns, component usage, and data loading patterns that MCP servers don't provide.

1時間の導入数
2
GitHub Stars
237
更新日
11月13日
medusajs
公式

storefront-best-practices

ALWAYS use this skill when working on ecommerce storefronts, online stores, shopping sites. Use for ANY storefront component including checkout pages, cart, payment flows, product pages, product listings, navigation, homepage, or ANY page/component in a storefront. CRITICAL for adding checkout, implementing cart, integrating Medusa backend, making a store agent-friendly for AI shopping agents, or building any ecommerce functionality. Framework-agnostic (Next.js, SvelteKit, TanStack Start, React,

1時間の導入数
2
GitHub Stars
234
更新日
10月21日
medusajs
公式

building-storefronts

Load automatically when planning, researching, or implementing Medusa storefront features (calling custom API routes, SDK integration, React Query patterns, data fetching). REQUIRED for all storefront development in ALL modes (planning, implementation, exploration). Contains SDK usage patterns, frontend integration, and critical rules for calling Medusa APIs.

1時間の導入数
1
GitHub Stars
234
更新日
10月21日
medusajs
公式

creating-internal-agents

Use when building an internal admin-facing AI agent in a Medusa project. These agents are operated by merchants and store operators — not customers. Covers data models, module service, agent runtime (tools, system prompt, streamText), streaming API routes (NDJSON), and admin UI chat extensions. Load for any internal agent type: store operations assistant, product audit, cohort analysis, customer service tooling for support staff, etc. Do NOT use for customer-facing agents (storefront chatbots, b

1時間の導入数
1
GitHub Stars
234
更新日
10月21日