Verify Code Change for Openclaw

Openclaw Skills for running tests and app commands to verify code changes, capture failures, and prevent regressions.

dkgee
v1.0.0
Jul 11, 2026
0
573
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install verify-code-change

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install verify-code-change using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Verify Code Change?

Verify Code Change is an Openclaw Skills utility that runs your application's test or verification command after code edits and checks whether the result matches expectations.

It is built for fast, repeatable regression checks: it enforces a timeout, captures detailed logs and stack traces, and surfaces a clear pass/fail/timeout outcome so developers can validate changes locally or wire the same behavior into CI/CD and pre-commit workflows.

Verify Code Change Use Cases

  • After bug fixes or refactors when you need a quick regression check.
  • Before committing or pushing changes to confirm the suite still passes.
  • In CI/CD pipelines to automate build or test verification.
  • When a command might hang and you need timeout protection.
  • When you need full failure context, including logs and stack traces.
  • Across JavaScript, Python, Rust, Go, Java, or custom command workflows.

How Verify Code Change Works

  1. Provide a test_command plus optional expected_behavior and timeout values.
  2. The script runs from the project root and launches the command with Python 3.11+, asyncio, and subprocess.
  3. It streams execution logs while monitoring the process for hangs or excessive runtime.
  4. It evaluates the command result and any expected behavior checks to decide pass, fail, or timeout.
  5. It prints a success message, an error with stack trace, or a timeout warning for downstream automation.

Verify Code Change Setup

  1. Make sure you are in the project root directory.
  2. Use Python 3.11 or later; the skill relies on the standard library asyncio and subprocess modules.
  3. Run the verification helper with the test command you want to check.
python scripts/verify_code.py --test-command "npm test"
python scripts/verify_code.py --test-command "python -m pytest" --timeout 120
python scripts/verify_code.py --test-command "cargo test" --expected-behavior "All tests passed"
  1. Increase --timeout for slower suites and set --expected-behavior when you want a human-readable success target.
  2. Add the command to CI/CD or a pre-commit hook so Openclaw Skills can verify changes automatically before merge.

Verify Code Change Data Schema & Taxonomy

Openclaw Skills uses a command-centric verification schema: one command in, one execution result out. The skill does not define persistent databases or generated artifact files; outputs are emitted to stdout/stderr and can be captured by your terminal, CI logs, or report collectors.

Schema element Type Required Purpose Default
test_command string Yes Command to execute for verification None
expected_behavior string No Optional human-readable success criteria Empty
timeout integer (seconds) No Maximum runtime before aborting the process 60
execution_log text Emitted Detailed runtime output from the command N/A
result_status enum Emitted One of test passed, test failed, or timeout N/A
error_trace text Emitted on failure Full stack trace and error details N/A

Supported command taxonomy:

  • JavaScript: npm test, jest, mocha, vitest
  • Python: pytest, unittest
  • Rust: cargo test
  • Go: go test
  • Java: mvn test
  • Custom: any executable verification command

Verify Code Change Advanced Features

Openclaw Skills power features make this verifier useful in both local development and automation-heavy workflows.

  • Timeout enforcement prevents hung tests from blocking your workflow.
  • Result parsing turns raw process output into clear pass, fail, and timeout states.
  • Full error capture includes stack traces to speed up debugging.
  • Broad framework support covers JavaScript, Python, Rust, Go, Java, and custom commands.
  • CI/CD integration lets you gate merges and deployments on verification outcomes.
  • Pre-commit compatibility helps catch regressions before code is pushed.
  • Detailed execution logs make it easier to review failures in code review or automated reports.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*