Vizzly Testing Cli
- 34 repo stars
- Updated July 27, 2026
- vizzly-testing/cli
vizzly-testing-cli is a Claude Code plugin that runs local Vizzly visual regression tests in a TDD workflow before you commit.
About
vizzly-testing-cli is a Claude Code plugin wrapping the Vizzly visual testing CLI for local TDD-style UI checks. developers 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).
- 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
Vizzly Testing Cli by the numbers
- Data as of Jul 28, 2026 (Skillselion catalog sync)
/plugin install vizzly-testing-cli@vizzly-testing/cliAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 34 |
|---|---|
| Last updated | July 27, 2026 |
| Repository | vizzly-testing/cli ↗ |
What it does
Run Vizzly visual regression tests locally in a TDD loop so UI bugs are caught before you commit.
Who is it for?
Best when you want fast visual regression feedback on your machine without waiting for CI alone.
Skip if: Backend-only or API-only projects with no meaningful UI surface to snapshot.
What you get
You run visual checks locally, review failures, and fix UI regressions before committing so ship stays confident.
- Installed Vizzly visual testing CLI plugin
- Local visual check workflow before commits
- Documented failure review and regression status habits
By the numbers
- 1 plugin in the marketplace bundle
- Repository vizzly-testing/cli
- Catalog lists 8 GitHub stars at last fetch
Recommended Plugins
Aglabo DeckrdDocument-Driven Development framework for AI-assisted BDD workflows1
Alonw0 Python Debugger SkillA skill for Python debugging methods and best practices10
Asynkron Asynkron.TestrunnerA.NET global tool that wraps dotnet test, captures TRX results, tracks test history, and displays regression charts3
Avdlee Swift Testing Agent SkillAn agent skill focused entirely on Swift Testing, helping you write better tests, migrate from XCTest, improve test architecture, and adopt modern Swift testing patterns with confidence.431
Bocato Swift Testing Agent SkillAgent Skill providing expert Swift Testing guidance for AI coding tools: covering test doubles, fixtures, async patterns, XCTest migration, and testing best practices.78
Brandcast Signage Agent Benchmark KitAutomated quality assurance for Claude Code agents using LLM-as-judge evaluation.3How it compares
Visual regression CLI plugin, not a general unit-test skill or a production error-monitoring integration.
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.