Agent skill · software engineering · steipete
openclaw-testing
Choose proportional OpenClaw tests/checks, diagnose failures, route environment-sensitive or release proof to its owner.
Why this skill is useful
Adds specific commands and workflows for OpenClaw testing and CI processes that the AI wouldn't reliably generate on its own.
What it needs
Requires docker, jq installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 385,400 stars on the source repository.
What this skill does
OpenClaw Testing Proof policy PR CI = default broad proof. Change builds + focused tests pass → open ready PR. CI runs broad suites; never delay PR for pre-PR suite runs. Build unavailable before publication: when publication is already authorized, remote capacity is unavailable, and local execution is unqualified, push/open a draft PR with the exact missing build and capacity gap recorded. Defer that build to exact-head CI. Require its success before marking ready or merging. This changes proof timing only, not publication authority, source trust, credentials, owner approval, or merge gates. Automatic CI skips drafts. For a trusted canonical branch, use the existing ci.yml manual dispatch with targetref set to the full pushed head SHA (ghx workflow run ci.yml --repo openclaw/openclaw --ref main -f targetref=<sha>). Verify the selected checkout SHA and successful build-artifacts job cover the required build. CI's build:ci-artifacts omits full declaration emission. Keep uncovered proof pending. A skipped job or workflow-ref SHA is not build proof. Link the run in the PR, then use normal ready-PR CI and landing gates. Untrusted source keeps its secretless route. Before PR, prove narrowly: touched tests with pnpm test <file> --maxWorkers=1, targeted typecheck, lint, format. Prefer local proof for trusted, bounded work when dependencies and current host capacity are qualified. Local execution is optional: a focused command can still load a large compiler graph or expand to broad lanes. Choose remote proof deliberately. Use PR CI for broad proof; Crabbox/Testbox may cover expensive checks, a busy or unqualified local host, another OS/device, live providers/channels, long E2E, or heavy benchmarks. Acquire only when the command is ready and capacity is granted promptly. If queued, stop only the task-owned allocation; use PR CI or a safe local scope. Keep uncovered platform-specific proof pending. Never force heavy work onto a busy machine or chain providers. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills steipete/openclaw-testing