verify-changes

Automate end-to-end verification of code changes with diff review, test execution, and UI checks.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/zeveck/zskills --skill verify-changes-zeveck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-changes
Source: https://github.com/zeveck/zskills/tree/main/skills/verify-changes
Command: npx skills add https://github.com/zeveck/zskills --skill verify-changes-zeveck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Thoroughly verify all recent changes by reviewing diffs, validating unit/e2e tests, running all tests, and manually verifying UI changes with playwright-cli, then re-verify until clean and report results with recommendations.

Core Features & Use Cases

  • Diff review and test-coverage audit
  • Automated test execution and regression verification
  • UI verification with playwright-cli and structured result reporting

Quick Start

Instruct the model to run a verification pass on a target scope, for example: /verify-changes last 3.

Frequently Asked Questions about verify-changes

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

FAQPage Schema
How do I verify code changes end-to-end after modifying my working tree?

To verify code changes end-to-end, you can automate diff review, test coverage audits, test execution, and UI validation. This process dispatches verification agents to comprehensively check modifications and returns a structured results report with recommendations.

How do I run automated tests and UI verification on a specific git branch?

You can run automated tests and UI verification on a git branch by instructing the model to run a verification pass on a target scope, such as the last 3 commits. It audits test coverage, runs tests, and validates UI changes.

Can I validate UI changes with Playwright after committing code?

Yes, you can validate UI changes with Playwright. The verification process includes manual UI verification using playwright-cli to ensure interface modifications function correctly, alongside running unit and end-to-end tests.

What is the best way to audit test coverage for recent diffs?

The best way to audit test coverage for recent diffs is to use an automated verification pass that reviews the code changes and evaluates existing tests. It enforces comprehensive checks and re-verifies regressions until clean.

Do I need additional dependencies to run regression verification on my commits?

No additional dependencies are required to run regression verification on your commits. The process operates independently to dispatch verification agents, review diffs, execute tests, and re-verify regressions until the working tree is clean.