研究检索external-serviceclawhub未标认证来源可访问clear审计通过

check-deployment-status（检查部署状态）

Agent Skill

用于辅助云资源、部署、容器、基础设施和运维自动化任务。它适合让 Agent 检查配置、整理部署步骤、分析资源状态、生成排障思路或辅助云服务接入。使用时需要明确目标环境、账号权限、区域和资源组，区分本地测试与生产操作；涉及删除资源、重启服务、修改网络或权限配置时，应先确认影响范围。

总安装

4,872

周安装

203

GitHub Stars

公开资料未说明

下载量

1,624

OpenClaw

安装说明

本站只整理中文说明和来源信息，不托管安装包，也不代用户安装。

GitHub

来源数

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手，先确认命令和权限，再让它执行。

请帮我安装这个 Agent Skill：check-deployment-status（检查部署状态）
来源仓库：https://github.com/ajitsingh25/check-deployment-status
安装命令：
openclaw skills install check-deployment-status
安装前请先检查当前环境是否支持对应 CLI，并向我确认将要执行的命令、安装目录、联网范围和文件读写权限；确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill；本站只展示命令，不托管安装包，也不自动执行。

ClawHubOpenClaw

openclaw skills install check-deployment-status

简介

检查 PR 提交后的部署状态与 UCS 程序运行情况。

适合在 OpenClaw 中跟踪 CI/CD 流水线进度时使用。
通过 clawhub 安装，依赖持续部署 MCP 与 UCS 部署程序 MCP。
安装前建议确认目标环境权限与日志访问路径。check-deployment-status 属于研究检索类 Skill，可作为该场景下的辅助能力补充。
注意该技能仅反映当前状态，历史记录需结合其他工具追溯。

SKILL.md

name: check-deployment-status
description: Check deployment status of PRs and commits using continuous-deployment MCP and UCS deployer MCP. Use when user asks "is this deployed", "check deployment", "deployment status", "is PR merged and deployed", "check UP status", "introduced to production", or provides a GitHub PR URL and wants deployment info.

Check Deployment Status

Check whether a PR/commit is deployed to staging and production using the continuous-deployment MCP tools.

Usage

/check-deployment-status <PR-URL>           # Check deployment of a GitHub PR
/check-deployment-status <commit-hash>      # Check deployment of a specific commit
/check-deployment-status <service-name>     # List recent commits and their deployment status

Key Concepts

PR Head Commit != Merge Commit

When a PR is merged via SubmitQueue, the merge commit on main is DIFFERENT from the PR's head commit. The continuous-deployment system tracks the merge commit, not the PR head.

Workflow:

Get PR metadata → extract head SHA
Use findServiceCommits with search text to find the actual merge commit on main
Use getCommitDeploymentStatus with the merge commit hash

UP Deployment Stages

Stage	Meaning
Build created	Binary built from commit
Deployed to staging	Running on staging instances
Soaked	Staging soak period passed
Waited for deployment window	Outside deploy freeze windows
Introduced to production	Fully deployed to production — code is live

"Introduced to production" = fully deployed. Not partial, not in-progress. The commit is running on all production instances.

Deployment Status Values

Status	Meaning
`DEPLOYMENT_STATUS_DEPLOYED`	Commit is running in this environment
`DEPLOYMENT_STATUS_DEPLOYING`	Deployment in progress
(empty)	Not deployed to this environment

Step-by-Step Workflow

Step 1: Get PR Metadata

Use mcp__code-mcp__get_github_pull_request_metadata:

org: uber-code
repo: go-code
number: <PR number>

Extract: title, head SHA, merged status, base branch.

Step 2: Find Merge Commit

The PR head SHA won't be found in deployment system. Search for the merge commit:

Use mcp__continuous-deployment__continuousdeployment_findservicecommits:

service_name: <service-name>
filter: { search_text: "<keyword from PR title>", commited_after: "2026-02-25T00:00:00Z" }
offset: 0
limit: 5

The result includes the merge commit hash, serial number, and code review metadata linking back to the PR.

Step 3: Check Deployment Status

Use mcp__continuous-deployment__continuousdeployment_getcommitdeploymentstatus:

hash: <merge-commit-hash>
repository: gitolite@code.uber.internal:go-code
options: { scope: "SCOPE_ALL_SERVICES" }

Returns deployment status per service per environment (staging, production, bits-test-sandbox).

MCP Tools Reference

continuous-deployment MCP

Tool	Purpose
`findServiceCommits`	Search commits by service name, author, text, date range
`getCommitDeploymentStatus`	Get deployment status of a commit across all environments
`listServiceCommits`	List recent commits for a service (with serial-based pagination)
`getCommitsInDeployment`	List commits in a specific deployment task
`listCommitSegments`	Get deployment segments for a service
`getConfigForService`	Get continuous deployment config for a service

code-mcp

Tool	Purpose
`get_github_pull_request_metadata`	PR status, author, labels, SubmitQueue status
`get_github_pull_request_diff`	PR diff content
`get_github_pull_request_comments`	PR comments

UCS deployer MCP

Tool	Purpose
`ucsdeployer_status`	Rollout status for a specific deployment object
`deploystatemanager_read`	Read deploy state

Service-Name Only Mode

If only a service name is provided (no PR/commit):

Use mcp__continuous-deployment__continuousdeployment_listservicecommits:

service_name: <service-name>
offset: 0
limit: 5

Then check deployment status for each returned commit using Step 3.

Common Patterns

Stacked PRs

For stacked PRs, each PR may affect different services. Check deployment per-service:

PRs changing marketing-recommendations/ → check marketing-recommendations service
PRs changing ads-insights/ → check ads-insights service

Repository URI

For go-code monorepo, always use: gitolite@code.uber.internal:go-code

适合场景

OpenClaw 用户查找和安装 Skill 时

用户想查找某类 Agent Skill 时

需要根据任务场景推荐可安装能力包时

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明，方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用；具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

78.83%

按下载量换算1,280

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

external-service

该 Skill 可能调用第三方服务、云服务或外部模型 API，使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息，不托管安装包，不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源，正式发布前建议补源仓库或其他目录站核验。

来源信息

GitHub 仓库

github.com

/ajitsingh25/check-deployment-status

SKILL.md 来源

clawhub.ai

/ajitsingh25/check-deployment-status

继续浏览同类 Skills

更多研究检索 Skills（73,675）返回 Skills 目录

上一个 Skill

check-demo-analytics（检查演示分析）

用于辅助数据整理、表格处理、CSV/Excel 分析、指标计算和图表准备。它适合让 Agent 清洗字段、汇总数据、发现异常、生成统计口径或把分析结果转成可读说明。使用时需要确认数据来源、字段含义和时间范围，避免把样本数据当全量事实；涉及敏感数据、导出文件或批量写回时，应先确认权限和脱敏边界。

下一个 Skill

check-docs（检查文档）

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径，不要把未确认的信息写成确定结论；涉及对外文案时，还需要控制语气，避免过度营销或夸大能力。