Vizzly Testing Cli
vizzly-testing-cli is a Claude Code plugin for the Ship phase that runs local Vizzly visual regression tests in a TDD workflow before you commit.
by vizzly-testing · github.com/vizzly-testing/cli
Run Vizzly visual regression tests locally in a TDD loop so UI bugs are caught before you commit.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install vizzly-testing-cli@vizzly-testing/cliBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:vizzly-testing/cli") and the paste-ready config with skillselion.get_install_config("plugin:vizzly-testing/cli").
What it does
vizzly-testing-cli is a Claude Code plugin wrapping the Vizzly visual testing CLI for local TDD-style UI checks. Solo builders shipping web or component UIs install it to compare screenshots and catch layout regressions before commits land on main. The marketplace entry emphasizes changes, check, debug, failures, regression, review, and visual testing—signals of a pre-merge quality gate, not a production monitoring suite. It pairs naturally with frontend build work: you iterate in the editor, run visual checks from the CLI plugin, and fix diffs while context is fresh. Beginners can start with happy-path snapshots; advanced users wire it into habitual commit rituals. Confidence is relatively high because the description and testing category are explicit about purpose and timing (before commit).
Highlights
- Visual testing CLI with a local test-driven development workflow
- Catch UI regressions before commit using Vizzly’s check and review flow
- Debug failures, learn practices, and track status from the plugin keywords
- Single-plugin bundle from vizzly-testing/cli
- Focused on visual regression rather than unit or API test runners
Why builders use it
Small UI tweaks silently break layouts and you only notice regressions after merge or in production screenshots.
You run visual checks locally, review failures, and fix UI regressions before committing so ship stays confident.
At a glance
- Type - Plugin in Testing.
- Adoption - 0 installs, 8 stars, 0 votes.
FAQ
Who is vizzly-testing-cli for?
It is for developers using Claude Code who ship UI and want Vizzly’s visual testing CLI hooked into their local commit workflow.
When should I use vizzly-testing-cli?
Use it during Ship-phase testing whenever you change UI and want to catch visual regressions before you commit or open a PR.
How do I add vizzly-testing-cli to my agent?
Register the vizzly-testing/cli Claude Code plugins marketplace, install the single Vizzly testing plugin, then follow the repo README to run visual checks from your project root.
Comments
Share how you use vizzly-testing-cli, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.