Verify Changes

Verify Changes is a Quality skill for Claude Code, published by h0x91b in dev-3.0.

249 stars31 forkson h0x91b/dev-3.0Added 2026/09/02+1% in starsRepository updated 2026/09/01

agent-orchestrationai-agentsai-codingbunclaude-codecodexdeveloper-toolselectrobungemini-cligit-worktreekanbanproject-managementterminaltmux

Install in seconds

Install Verify Changes

Copy Verify Changes into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/h0x91b/dev-3.0/tree/main/change-logs/2026/07/25 ~/.claude/skills/25

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/h0x91b/dev-3.0.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: change-logs/2026/07/25/docs-verify-changes-skill.md in h0x91b/dev-3.0
Installs to: ~/.claude/skills/25
Collection: One of 11 skills cataloged from this repository
Category: Quality — 1418 skills

What Verify Changes does

Verify Changes covers what to test for code changes, including vitest scope, mocking patterns, flake reproduction, and coverage expectations. Use it when validating a change against repo-specific verification gates and browser QA requirements.

Verify Changes is cataloged under Quality on DirSkills. Verify Changes comes from a repository tagged agent-orchestration, ai-agents, ai-coding, bun and claude-code.

Documentation

README

From the original repository

Moved the testing detail out of AGENTS.md into a new repo-local /verify-changes skill (which vitest config covers what, what a change needs covered, house style, mocking Electrobun RPC and useT(), reproducing flakes under load, coverage expectations), leaving the two verification gates and the browser-QA mandate inline where they cannot be missed. The 1-5 tip coolness rubric now lives on a TipScore union type in src/mainview/tips.ts instead of being restated in prose, and the key-files list gained the entries an agent is most likely to overlook: shared types, the RPC handler barrel, the reducer, design tokens, the keymap, shipped skill text, CLI exit codes, CI workflows, and the decision records.

Commands Verify Changes provides

Slash commands named in this skill’s SKILL.md, listed in the order they first appear.

/verify-changes

Frequently asked about Verify Changes

What else does h0x91b publish alongside Verify Changes?
Verify Changes is one of 11 skills that DirSkills catalogs from h0x91b/dev-3.0, the repository it ships in. Its siblings there include Artifact Sharing, Ask Dev3 and Ask Dev3. Each one is a separate skill with its own page in this directory, installs the same way Verify Changes does, and is maintained by h0x91b in that same repository. The rest of the collection is listed on the h0x91b/dev-3.0 page.
How does Verify Changes compare to other Quality skills?
Verify Changes ranks #1293 by stars among the 1418 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Verify Changes against them. Open each page to compare what they document and how they install.