QualityTypeScript

Verify Changes

by h0x91b

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/.claude/skills/verify-changes ~/.claude/skills/verify-changes

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
.claude/skills/verify-changes/SKILL.md in h0x91b/dev-3.0
Installs to
~/.claude/skills/verify-changes
Collection
One of 11 skills cataloged from this repository
Category
Quality1418 skills

What Verify Changes does

Verify Changes explains how to test and verify work in dev-3.0, including which Vitest config covers each area, how to mock RPC and i18n providers, and what coverage is expected. Use it when writing tests, investigating failures, or preparing a change for review.

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

verify-changes — testing and verification in dev-3.0

The two hard gates (lint + touched tests before push, full suite before a PR) live in AGENTS.md and apply whether or not you read this file. Everything here is the detail behind them: which runner covers what, how to write a test that fits, and what "enough" means.

Which config runs what

Vitest with happy-dom and React Testing Library. Three configs, three independent processes:

Config Covers Script
vitest.config.ts renderer (src/mainview/) part of bun run test
vitest.config.bun.ts backend (src/bun/) bun run test:bun
vitest.config.cli.ts CLI (src/cli/) bun run test:cli

This is the opening of the README. Read the full README on GitHub.

Commands Verify Changes provides

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

  • /debug-ui

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 #1292 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.

More from h0x91b/dev-3.0

Verify Changes is one of 11 skills cataloged on DirSkills from h0x91b/dev-3.0.

See all 11 skills
📎
1h ago

Artifact Sharing

Artifact Sharing folds a multi-file report into one self-contained HTML file, publishes it as a secret GitHub gist, and checks the preview URL before returning it. Use it when you need to share a report link from an agent workflow.
Automation
24931
🧭
1h ago

Ask Dev3

Ask Dev3 routes questions about using dev3 to the right workflow and explains the intended steps instead of guessing. Use it when someone asks how to do something in dev3, including onboarding, verification, tmux, multi-agent work, or troubleshooting.
AI Engineering
24931
🧭
1h ago

Ask Dev3

Ask Dev3 answers how-to questions about dev3 by pointing users to the intended flow, relevant decisions, and light troubleshooting steps. It is used when someone asks how a dev3 feature is done or why it works that way.
AI Engineering
24931
🖥️
1h ago

Debug UI

Debug UI drives the dev-3.0 app in headless Chromium to verify UI changes, reproduce visual bugs, take screenshots, and check console errors. Use it when you need to test the running interface instead of guessing from code.
Quality
24931
🐞
1h ago

Dev3 Bug Hunter

Dev3 Bug Hunter runs read-only bug-hunting sessions with a seeded starting area and analysis style. It reports findings in a terminal-friendly format and can turn critical or medium issues into follow-up tasks that must reproduce the bug first.
Quality
24931
🧠
1h ago

Dev3 Refactor Shrink

Dev3 Refactor Shrink cuts the token footprint of the Dev3 Claude skill by removing duplicated protocol, shortening the invoke output, and densifying the shared skill body. Use it when you need the Dev3 agent instructions to fit into fewer tokens.
AI Engineering
24931