workclaw-change-verification

Map changed files to minimal verification commands and run them.

154|1|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/haojing8312/WorkClaw --skill workclaw-change-verification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workclaw-change-verification
Source: https://github.com/haojing8312/WorkClaw/tree/main/.agents/skills/workclaw-change-verification
Command: npx skills add https://github.com/haojing8312/WorkClaw --skill workclaw-change-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps developers determine what "verified" means after changes touch runtime code, tests, skill assets, packaging, or build behavior in the WorkClaw repository and ensures the minimal honest verification is executed before claiming completion.

Core Features & Use Cases

  • Map changes to surfaces: Identify which changed files affect React runtime, Tauri backend, sidecar/adapters, Rust packages, builtin skills, packaging, or end-to-end runtime flows.
  • Select minimal command set: Recommend and run the smallest, honest set of repository commands (for example pnpm test:sidecar, pnpm test:rust-fast, pnpm test:builtin-skills, pnpm test:e2e:runtime, pnpm build:runtime) that visibly cover the touched surface.
  • Concrete reporting: Produce a verification summary listing commands run, pass/fail results, which changed areas each command covered, any still-unverified areas, and a clear verification verdict.
  • Use case: A pull request modifying both frontend UI flow and a sidecar adapter triggers combined frontend e2e and sidecar tests to avoid regressions before merging.

Quick Start

Run the smallest honest set of repository verification commands that cover your changed files, for example run pnpm test:rust-fast for Rust logic changes or pnpm test:builtin-skills when skill assets changed.

Frequently Asked Questions about workclaw-change-verification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify runtime changes in a Tauri and React repository before merging?

To verify runtime changes in a Tauri and React repository, map modified files to affected surfaces like the frontend or backend, then run the minimal set of pnpm test commands to cover those specific areas before merging.

What is the minimal testing strategy for sidecar adapter and Rust package modifications?

The minimal testing strategy for sidecar adapter and Rust package modifications involves mapping the changed files to affected runtime surfaces, then executing targeted commands like pnpm test:sidecar and pnpm test:rust-fast to confirm logic integrity.

How do I map changed files to the correct pnpm test commands?

Map changed files to the correct pnpm test commands by identifying whether the modifications affect React frontend, Tauri backend, sidecar adapters, Rust packages, or builtin skills, then selecting the matching repository command.

Do I need to run all repository tests when only builtin skill assets change?

You do not need to run all repository tests when only builtin skill assets change; instead, run the targeted pnpm test:builtin-skills command to verify those specific changes and reduce unnecessary testing overhead.

What should a verification report include after running end-to-end runtime tests?

A verification report after running end-to-end runtime tests should include the commands executed, pass or fail results, the changed areas each command covered, any remaining unverified areas, and a clear final verification verdict.

Can I use this approach to verify both frontend UI flow and sidecar adapter changes simultaneously?

You can verify both frontend UI flow and sidecar adapter changes simultaneously by triggering combined e2e and sidecar tests, such as pnpm test:e2e:runtime, to prevent regressions across interconnected runtime flows.