verify-changes

Audit recent codebase changes across worktrees, branches, or commits.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/zillabunny/GoblinVolleyball-1.1 --skill verify-changes-zillabunny
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-changes
Source: https://github.com/zillabunny/GoblinVolleyball-1.1/tree/main/.claude/skills/verify-changes
Command: npx skills add https://github.com/zillabunny/GoblinVolleyball-1.1 --skill verify-changes-zillabunny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured workflow to audit recent changes, verify that diffs are addressed, validate test coverage, and ensure UI changes are properly reviewed with Playwright CLI, culminating in a clear remediation plan.

Core Features & Use Cases

  • Inventorying diffs across worktrees, branches, or last N commits
  • Verifying that unit/e2e tests exist and pass, and that UI changes are manually validated when needed
  • Generating a formal verification report with recommendations and next steps

Quick Start

Follow the /verify-changes [scope] command to start a full verification pass across the selected scope.

Frequently Asked Questions about verify-changes

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

FAQPage Schema
How do I verify recent code changes across git branches and worktrees?

You can verify recent code changes by running a structured audit that inventories diffs across worktrees, branches, or the last N commits to ensure all modifications are reviewed and addressed. This process covers diff analysis and test validation.

Can I run Playwright UI tests as part of an automated change verification workflow?

Yes, automated change verification can incorporate optional UI verification via Playwright CLI to validate UI changes. It generates a formal report with actionable recommendations after checking tests and diffs.

How do I check if unit and e2e tests exist and pass after modifying a codebase?

Checking if tests exist and pass is handled by executing a verification pass that validates test coverage for recent changes. It confirms test execution success and identifies missing tests for modified code.

What is the best way to generate a remediation plan for unverified code diffs?

The best way to generate a remediation plan is to run an automated change verification audit that reviews diffs, executes tests, and validates UI changes. This produces a formal report with recommendations and next steps.

Does automated change verification support multiple git worktrees and commit ranges?

Yes, automated change verification supports scoping across multiple git worktrees, branches, or the last N commits. This allows you to target specific commit ranges and inventory all relevant diffs accurately.