$ loading_
帮助开发与运维团队运行、排查并总结 OpenClaw 发布 CI 与发布前检查流程
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "release-openclaw-ci" 技能： 1. 下载 https://raw.githubusercontent.com/openclaw/openclaw/main/.agents/skills/release-openclaw-ci/SKILL.md 2. 保存为 ~/.claude/skills/release-openclaw-ci/SKILL.md 3. 装好后重载技能，告诉我可以用了
请启动 OpenClaw 全量发布 CI，持续监控各阶段状态，并在失败时标注失败步骤、错误日志摘要和可能原因。
返回 CI 执行状态、关键阶段进度、失败节点说明及初步排障建议。
请执行 OpenClaw 发布检查，包括 live provider gates、安装/更新验证证明，以及 release-secret 预检，并汇总所有未通过项。
输出各项门禁检查结果、通过/失败原因，以及需要处理的风险清单。
根据本次 OpenClaw 发布流程的 CI 日志与检查结果，生成一份简洁总结，包含整体结论、主要问题、影响范围和建议下一步。
一份适合团队同步的发布总结，便于快速了解状态与后续动作。
Use this with $release-openclaw-maintainer and $openclaw-testing when a release candidate needs full validation, install/update proof, live provider checks, or CI recovery.
$one-password for secret reads/writes: one persistent tmux session, targeted items only, no secret output.gh run view polling loops; REST quota is easy to burn.Before full release validation:
node .agents/skills/release-openclaw-ci/scripts/verify-provider-secrets.mjs --required openai,anthropic,fireworks
gh api rate_limit --jq '.resources.core'
git status --short --branch
git rev-parse HEAD
1Password service-account values are the first source for release provider preflight. Inject those exact targeted keys first, then run the verifier; use ambient env only when it was already intentionally injected for this release. The script prints only provider status and HTTP class, never tokens.
Start product performance evidence as early as the release SHA exists, in parallel with other release work:
gh workflow run openclaw-performance.yml \
--repo openclaw/openclaw \
--ref main \
-f target_ref=<release-sha> \
-f profile=release \
-f repeat=3 \
-f deep_profile=false \
-f live_openai_candidate=false \
-f fail_on_regression=false
Prefer the trusted workflow on main, target the exact release SHA:
gh workflow run full-release-validation.yml \
--repo openclaw/openclaw \
--ref main \
-f ref=<release-sha> \
-f provider=openai \
-f mode=both \
-f release_profile=full \
-f rerun_group=all
Use release_profile=stable unless the operator explicitly asks for the broad advisory provider/media matrix. Use narrow rerun_group after focused fixes.
Publish with openclaw-release-publish.yml using release_profile=from-validation
unless a maintainer intentionally wants to cross-check a specific profile; the
publish workflow reads the effective profile from the full-validation manifest.
Use the summary helper instead of repeated raw polling:
node .agents/skills/release-openclaw-ci/scripts/release-ci-summary.mjs <full-release-run-id>
Then watch only when useful:
gh run watch <full-release-run-id> --repo openclaw/openclaw --exit-status
Stop watchers before ending the turn or switching strategy.
…
帮助团队检索重复的 PR 与问题单，并自动分组同步重复状态。