workclaw-change-verification

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.