Choose suitable tests and checks for OpenClaw changes, then investigate failures using the relevant evidence. It guides local validation and directs environment-dependent or release testing to the appropriate procedures, keeping checks tied to the changed behavior.
Choose proportional OpenClaw tests/checks, diagnose failures, route environment-sensitive or release proof to its owner.
Select tests and checks for OpenClaw changes and investigate failures. The skill chooses among checks for changed files, type checking, static code analysis, focused tests, and builds. For failures in CI, an automated validation environment, it identifies the relevant commit and job, then distinguishes product issues from problems with the test environment, infrastructure, or credentials.
It is intended for developers verifying bug fixes or deciding what to test after changes to SDK or plugin behavior. It also helps select validation that needs dedicated environments or procedures, including package installation, Docker, live services, and release candidates.
Follow OpenClaw documentation and the AGENTS.md that applies to the changed files, using pnpm or repository runner scripts. Do not run tools from untrusted contributors locally; use a validation environment without credentials. Testing an operating Gateway or real data requires explicit approval for each task. Passing part of release validation does not itself authorize publication.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 19, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
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.
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. Use the smallest profile proven for the selected workload.
Never rerun or re-push just for green. Fix real failures; read available CI failure classification before attributing red.
Prove changed contract, complete required gates, finish. Broaden/repeat only for changed inputs, failures, or named unresolved risk.
Follow scoped AGENTS.md; authoring/reviewing tests: use
boundary guide
and test-audit.
Select proof for touched contract; reuse valid proof (rerun for changed inputs or missing coverage); finish workflow's required gates within user/host limits; report unrun checks and gaps. Prove user-visible behavior through real flow when feasible; external APIs need live contract proof; isolated mock-Gateway harness = valid channel boundary proof. Docs-only: docs sanity and git diff --check.
Runtime defect: reproduce real entry point; rerun it + relevant siblings.
Trusted source: pnpm changed:lanes --json, focused tests + targeted typecheck/lint/format; pnpm check:changed = optional smart local check.
Public SDK/plugin contract: representative consumers, not all-plugin sweep.
Build output, lazy imports, package boundaries: include pnpm build.
Workflow: git diff --check + pnpm check:workflows.
Docs only: relevant docs/link/format checks + git diff --check; no runtime tests.
Read on demand: local commands, Crabbox, OpenClaw remote setup, package/Docker proof, release CI, plugin release matrix, Docker authoring, channel skill/ Control UI E2E.
An isolated mock-Gateway harness is valid channel boundary proof; state live gaps. Prove user-visible behavior through the real flow when feasible; external APIs require live contract proof. Read the scoped channel/platform guide for live-channel or native-app work. Telegram claims require Test Server userbot proof with Convex-leased credentials. Platform claims require real-device evidence; macOS permission proof requires a stable signed app.
Release proof: preserve candidate/Tooling SHAs; never grants publication authority.
OPENCLAW_VITEST_FS_MODULE_CACHE_PATH
values or run serially; checks can run Vitest too. Repository wrappers only,
never raw Vitest. Prepared linked worktrees: node scripts/check-changed.mjs
and node scripts/run-vitest.mjs <file> --maxWorkers=1 avoid pnpm reconciliation.pnpm test:ci-failed <pr>; read pre-existing/new/unknown classification.pnpm test:ci-failed <pr> --run until selected tests pass locally → push once.--run enables OPENCLAW_NODE_TEST_PLAN_CONTINUE_ON_FAILURE=1: collect ordinary failures across selected configs, while infrastructure failures still stop; use the same opt-in for manual focused reruns.gh run rerun to chase green; never local full suite for CI repair.Narrow baseline, snapshot, ignore, and expected-failure exceptions are implementer decisions only when each entry is verified against source and the PR records its reason (for example, tool-owned metadata in an upgrade snapshot while user data stays exact). Never mask a real regression or user-data change. Blanket or unverified exceptions need approval. Exact shrink-only ratchet updates are maintenance.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Set up and authenticate the 1Password CLI, then supply stored passwords and API keys to commands or configuration. The skill covers desktop integration, service accounts, and interactive sign-in while keeping secrets out of chat and logs.
Route requests from OpenClaw to external coding agents such as Claude Code or Cursor. Start or continue sessions using ACP, a protocol for connecting agents, or relay prompts directly through acpx while preserving conversation context.
Add a model provider to OpenClaw and verify it with a real response. The skill validates configuration, keeps credentials in environment or file references, and reports test results and any default model changes.
Prepare an agent activity transcript for a GitHub pull request or issue. Extract relevant prompts, decisions, and results from local logs, remove sensitive material, and preview the edited record before separately authorized publication.
Manage Apple Notes on macOS through memo, a command-line tool. Create, browse, search, edit, delete, and move notes between folders, or export selected notes to HTML or Markdown for use outside the app.
Manage Apple Reminders from your Mac with remindctl, a terminal tool. View tasks by date, add or edit reminders, organize lists, and mark tasks complete or delete them, including personal to-dos that sync to iOS.