$ loading_
帮助开发者选择并执行 OpenClaw 测试、CI 校验与发布验证的最优路径。
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "openclaw-testing" 技能： 1. 下载 https://raw.githubusercontent.com/openclaw/openclaw/main/.agents/skills/openclaw-testing/SKILL.md 2. 保存为 ~/.claude/skills/openclaw-testing/SKILL.md 3. 装好后重载技能，告诉我可以用了
我刚改了 OpenClaw 的输入处理逻辑，请帮我判断先跑哪些最便宜且足够安全的测试：单测、CI checks、Docker E2E 还是发布验证？请按优先级给出建议，并说明为什么。
给出分层测试建议、执行顺序，以及每一步覆盖的风险说明。
OpenClaw 的 CI 有两个检查失败了。请根据失败类型判断应该只重跑失败项、扩大到相关测试，还是进入调试流程，并给出具体操作建议。
输出针对失败场景的重跑或调试决策树，并附上推荐命令或步骤。
我要发布 OpenClaw 新版本。请设计一个发布前验证方案，覆盖关键 CI、Docker E2E、回归测试和最终发布检查，并尽量控制验证成本。
提供兼顾风险与成本的发布验证清单，明确必跑项与可选项。
Use this skill when deciding what to test, debugging failures, rerunning CI, or validating a change without wasting hours.
docs/reference/test.md for local test commands.docs/ci.md for CI scope, release checks, Docker chunks, and runner behavior.AGENTS.md files before editing code under a subtree.Prove the touched surface first. Do not reflexively run the whole suite.
pnpm changed:lanes --json, then pnpm check:changed (delegates to Crabbox/Testbox)pnpm test:changedpnpm test <path-or-filter> -- --reporter=verbosenode scripts/run-vitest.mjs <path-or-filter>pnpm gates, that is usually delegated Blacksmith
Testbox through Crabbox, e.g. node scripts/crabbox-wrapper.mjs run --provider blacksmith-testbox ... -- env OPENCLAW_CHECK_CHANGED_REMOTE_CHILD=1 OPENCLAW_CHANGED_LANES_RAW_SYNC=1 corepack pnpm check:changed. For direct AWS
Crabbox proof, omit --provider and let .crabbox.yaml choose AWS.git diff --check, workflow syntax/lint (actionlint when available)pnpm docs:list, docs formatter/lint only if docs tooling changed or requestedpnpm test, or full pnpm check unless the user asks or the change genuinely requires it.scripts/committer "<msg>" <paths...> when committing; stage only your files.pnpm install, retry once, then report the first actionable error.pnpm test*, pnpm check*, pnpm crabbox:run, or scripts/committer until
you have verified pnpm will not reconcile or reinstall dependencies. Use
node scripts/run-vitest.mjs for tiny local proof, node scripts/crabbox-wrapper.mjs for Testbox, and git commit --no-verify only
after the relevant remote or node-wrapper proof is already clean.provider=aws and cbx_... ids. Delegated
Blacksmith Testbox through Crabbox uses provider=blacksmith-testbox,
syncDelegated=true, and tbx_... ids. Both satisfy "remote proof" when the
requested proof surface allows either.blacksmith testbox list.
Use blacksmith testbox list --all or blacksmith testbox status <tbx_id>
before reporting cloud state.pnpm changed:lanes --json
pnpm check:changed # Crabbox/Testbox changed typecheck/lint/guards; no Vitest
pnpm test:changed # cheap smart changed Vitest targets
pnpm verify # full check, then full Vitest
OPENCLAW_TEST_CHANGED_BROAD=1 pnpm test:changed
pnpm test <path-or-filter> -- --reporter=verbose
…
帮助团队检索重复的 PR 与问题单，并自动分组同步重复状态。