$ ~/registry/skill/openclaw-agents-skills-openclaw-testing

SKILL

openclaw-testing

Name: openclaw-testing
Author: openclaw

帮助开发者选择并执行 OpenClaw 测试、CI 校验与发布验证的最优路径。

星标

★ 383,594

来源

GitHub

更新于

2026-07-20

// 安全评估需留意

仅提示词，不执行代码
开源可审计
社区验证· 377.5k

总评

该技能材料表现为用于测试决策与命令建议的 prompt-only 开源技能，未声明需要密钥、远程端点或内置数据外发能力。整体风险较低，但其文档会建议运行本地测试/CI命令，实际使用时仍应由操作者自行审查将要执行的命令范围。

凭证密钥低风险

材料明确标注“无”密钥/环境变量；README 中也未见要求用户提供 API token 或长期凭证。若后续按其建议使用外部 CI/云测试基础设施，相关凭证不属于该技能本身声明范围。

网络外发低风险

已声明无远程端点，且作为 prompt-only 技能本身不具备主动联网或传输数据的内建机制。文档虽提到 GitHub Actions、AWS/Blacksmith/Testbox/Crabbox 等测试路径，但这是建议性的操作说明，不等同于该技能自动向这些端点外发数据。

代码执行需留意

README 大量提供本地命令与测试/CI重跑命令（如 pnpm、node、git、actionlint、Docker 相关流程），说明该技能的预期用途是指导操作者执行本机开发/测试命令。由于其本质是提示型技能而非可执行二进制，代码执行风险主要来自后续人工采纳这些命令，属需留意而非红旗。

数据访问需留意

文档建议检查 diff、读取 docs/AGENTS.md、运行测试、必要时安装依赖与提交代码，意味着实际使用场景可能涉及访问源码树、测试文件、工作区元数据与提交内容。但材料未显示该技能自身具有超出开发测试常规所需的自动读写权限或过度授权要求。

来源供应链低风险

来源为 GitHub 开源仓库，系统标记为 open-source，社区采用度极高（约 377k star），这些都是明显的降风险因素。虽未声明许可证且维护状态未知，仍未见闭源、失联、可疑分发源或恶意注入迹象；就现有材料看，供应链风险偏低。

安全建议

仅将其作为测试/CI决策参考，执行前逐条审查 README 中建议的命令。
若在受限环境中使用，优先禁用或隔离 Docker、远程 CI/云测试相关步骤，除非确有需要。
在执行 pnpm install、测试重跑或提交命令前，确认当前工作区与依赖状态，避免对无关文件产生影响。
补充核验仓库许可证、最近提交记录与发布流程，以完善供应链判断。

审计模型: gpt-5.4 · 2026-06-16

// 安装

复制安装指令，让 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. 装好后重载技能，告诉我可以用了

// 下载

下载 SKILL.md机读安装清单 ↗

// 用法示例

定位失败测试路径

输入

我刚改了 OpenClaw 的输入处理逻辑，请帮我判断先跑哪些最便宜且足够安全的测试：单测、CI checks、Docker E2E 还是发布验证？请按优先级给出建议，并说明为什么。

预期产出

给出分层测试建议、执行顺序，以及每一步覆盖的风险说明。

重跑失败的 CI 检查

输入

OpenClaw 的 CI 有两个检查失败了。请根据失败类型判断应该只重跑失败项、扩大到相关测试，还是进入调试流程，并给出具体操作建议。

预期产出

输出针对失败场景的重跑或调试决策树，并附上推荐命令或步骤。

发布前验证方案

输入

我要发布 OpenClaw 新版本。请设计一个发布前验证方案，覆盖关键 CI、Docker E2E、回归测试和最终发布检查，并尽量控制验证成本。

预期产出

提供兼顾风险与成本的发布验证清单，明确必跑项与可选项。

// 文档

OpenClaw Testing

Use this skill when deciding what to test, debugging failures, rerunning CI, or validating a change without wasting hours.

Read First

docs/reference/test.md for local test commands.
docs/ci.md for CI scope, release checks, Docker chunks, and runner behavior.
Scoped AGENTS.md files before editing code under a subtree.

Default Rule

Prove the touched surface first. Do not reflexively run the whole suite.

Inspect the diff and classify the touched surface:
- normal source checkout, source change: pnpm changed:lanes --json, then pnpm check:changed (delegates to Crabbox/Testbox)
- normal source checkout, tests only: pnpm test:changed
- normal source checkout, one failing file: pnpm test <path-or-filter> -- --reporter=verbose
- Codex worktree or linked/sparse checkout, one/few explicit files: node scripts/run-vitest.mjs <path-or-filter>
- Codex worktree or linked/sparse checkout, changed gates or anything broad: use the Crabbox wrapper with the provider that matches the proof surface. For maintainer heavy 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.
- workflow-only: git diff --check, workflow syntax/lint (actionlint when available)
- docs-only: pnpm docs:list, docs formatter/lint only if docs tooling changed or requested
Reproduce narrowly before fixing.
Fix root cause.
Rerun the same narrow proof.
Broaden only when the touched contract demands it.

Guardrails

Do not kill unrelated processes or tests. If something is running elsewhere, treat it as owned by the user or another agent.
Do not run expensive local Docker, full release checks, full pnpm test, or full pnpm check unless the user asks or the change genuinely requires it.
Prefer GitHub Actions for release/Docker proof when the workflow already has the prepared image and secrets.
Use scripts/committer "<msg>" <paths...> when committing; stage only your files.
If deps are missing, run pnpm install, retry once, then report the first actionable error.
In a Codex worktree or linked/sparse checkout, do not run direct local 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.
For remote proof, use the Crabbox wrapper first, but name the actual backend. Direct AWS Crabbox uses 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.
Do not infer "no Testbox is running" from plain blacksmith testbox list. Use blacksmith testbox list --all or blacksmith testbox status <tbx_id> before reporting cloud state.
Reuse only an id/slug created in this operator session unless explicitly coordinating with another lane. If Testbox queues, fails capacity, or cannot allocate, report the blocker or switch to direct AWS Crabbox only when that still proves the requested surface.

Local Test Shortcuts

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

…

查看完整文档 ↗

用于运行、重跑、调试并解读 OpenClaw Parallels 安装与冒烟检查结果

openclaw装→

$ loading_

请帮我安装 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 还是发布验证？请按优先级给出建议，并说明为什么。

预期产出

给出分层测试建议、执行顺序，以及每一步覆盖的风险说明。

重跑失败的 CI 检查

输入

OpenClaw 的 CI 有两个检查失败了。请根据失败类型判断应该只重跑失败项、扩大到相关测试，还是进入调试流程，并给出具体操作建议。

预期产出

输出针对失败场景的重跑或调试决策树，并附上推荐命令或步骤。

发布前验证方案

输入

我要发布 OpenClaw 新版本。请设计一个发布前验证方案，覆盖关键 CI、Docker E2E、回归测试和最终发布检查，并尽量控制验证成本。

预期产出

提供兼顾风险与成本的发布验证清单，明确必跑项与可选项。

// 文档

OpenClaw Testing

Use this skill when deciding what to test, debugging failures, rerunning CI, or validating a change without wasting hours.

Read First

docs/reference/test.md for local test commands.
docs/ci.md for CI scope, release checks, Docker chunks, and runner behavior.
Scoped AGENTS.md files before editing code under a subtree.

Default Rule

Prove the touched surface first. Do not reflexively run the whole suite.

Inspect the diff and classify the touched surface:
- normal source checkout, source change: pnpm changed:lanes --json, then pnpm check:changed (delegates to Crabbox/Testbox)
- normal source checkout, tests only: pnpm test:changed
- normal source checkout, one failing file: pnpm test <path-or-filter> -- --reporter=verbose
- Codex worktree or linked/sparse checkout, one/few explicit files: node scripts/run-vitest.mjs <path-or-filter>
- Codex worktree or linked/sparse checkout, changed gates or anything broad: use the Crabbox wrapper with the provider that matches the proof surface. For maintainer heavy 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.
- workflow-only: git diff --check, workflow syntax/lint (actionlint when available)
- docs-only: pnpm docs:list, docs formatter/lint only if docs tooling changed or requested
Reproduce narrowly before fixing.
Fix root cause.
Rerun the same narrow proof.
Broaden only when the touched contract demands it.

Guardrails

Do not kill unrelated processes or tests. If something is running elsewhere, treat it as owned by the user or another agent.
Do not run expensive local Docker, full release checks, full pnpm test, or full pnpm check unless the user asks or the change genuinely requires it.
Prefer GitHub Actions for release/Docker proof when the workflow already has the prepared image and secrets.
Use scripts/committer "<msg>" <paths...> when committing; stage only your files.
If deps are missing, run pnpm install, retry once, then report the first actionable error.
In a Codex worktree or linked/sparse checkout, do not run direct local 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.
For remote proof, use the Crabbox wrapper first, but name the actual backend. Direct AWS Crabbox uses 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.
Do not infer "no Testbox is running" from plain blacksmith testbox list. Use blacksmith testbox list --all or blacksmith testbox status <tbx_id> before reporting cloud state.
Reuse only an id/slug created in this operator session unless explicitly coordinating with another lane. If Testbox queues, fails capacity, or cannot allocate, report the blocker or switch to direct AWS Crabbox only when that still proves the requested surface.

Local Test Shortcuts

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

…

查看完整文档 ↗