Expert reg-suit review skill for evaluating rendered UI image baselines, thresholds, snapshot storage, report artifacts, and visual QA release readiness.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
86
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
Registry metadata indicates a reviewed listing.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 16/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
Listing has review metadata.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Required evidence gates are covered (5/6 signals complete).
Source repository/provenance is listed.
Required in this preset
Review metadata is present.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
5/6 steps complete with no blocking gaps for this preset.
triage
Source/provenance metadata is available.
triage
Review metadata is available.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
No required blockers for this timeline preset.
Prerequisite readiness
5 prerequisites to line up before setup. Includes a review or approval gate.
Safety & privacy surface
4 safety and 3 privacy notes across 3 risk areas. Review closely: network access.
| Platform | Support | Install path |
|---|---|---|
| claude-code | Native | .claude/skills/<skill-name>/SKILL.md |
| codex | Native | .agents/skills/<skill-name>/SKILL.md |
| windsurf | Native | .windsurf/skills/<skill-name>/SKILL.md |
| gemini | Native | .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md |
| cursor | Adapter | .cursor/rules/<skill-name>.mdc |
| cli | Manual | AGENTS.md or tool-specific context file |
# Trigger
"Apply the reg-suit visual regression review capability pack to this UI change."
# Required output
1) reg-suit package/source version and config inventory
2) Baseline, actual image, threshold, and report review
3) Visual-diff findings with release-blocking and non-blocking issues
4) Validation plan and merge, hold, or request-changes recommendationThis capability pack is pinned to reg-suit CLI package 0.14.5, the reg-suit source release v0.14.6, npm metadata, and source files verified on 2026-06-03. The source release contains packages/reg-suit-cli/package.json with package name reg-suit and version 0.14.5.
Prefer current reg-suit source, npm metadata, and repository documentation over model memory for CLI commands, plugin names, threshold options, and report behavior.
This is not a Playwright E2E testing skill, a generic rendered-page workflow, or an after-edit hook. Use it for human-in-the-loop review of reg-suit visual regression artifacts: baselines, actual image sets, diff reports, thresholds, storage plugins, notification plugins, and release decisions.
regconfig.json and inventory core.workingDir, core.actualDir, thresholdRate, thresholdPixel, matchingThreshold, antialias handling, x-img-diff settings, and concurrency.regconfig.json and plugin reviewSKILL.md-style instructions for UI artifact review.regconfig.json and configured plugin listIssue: The report shows widespread pixel drift
Fix: Check rendering environment, fonts, viewport size, animation state, and capture timing before accepting a broad baseline update.
Issue: The target branch has no expected images
Fix: Review the key generator plugin, branch/commit key, storage destination, and CI checkout depth before treating every image as new.
Issue: Thresholds hide meaningful changes
Fix: Lower the threshold or split critical pages into stricter scenarios. Escalate changes affecting navigation, forms, pricing, permissions, or primary actions.
Issue: Report links are unavailable after CI finishes
Fix: Check publisher plugin settings, bucket permissions, report retention, and whether notification plugins point reviewers to the same report generated by the run.
Issue: Baselines keep changing without product changes
Fix: Stabilize fonts, viewport, locale, time, seeded data, animation state, and network fixtures before approving new images.
regconfig.json found and reviewed.Show that Reg-suit Visual Regression Review Capability Pack Skill is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/skills/reg-suit-visual-regression-review-capability-pack)Reg-suit Visual Regression Review Capability Pack Skill side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Expert reg-suit review skill for evaluating rendered UI image baselines, thresholds, snapshot storage, report artifacts, and visual QA release readiness. Open dossier | Expert Vitest coverage planning skill for choosing providers, scoping reports, setting thresholds, triaging gaps, and designing practical coverage gates. Open dossier | Expert Spectral review skill for auditing OpenAPI contracts, OAS rulesets, lint results, schema drift, CI gates, and API release readiness. Open dossier | Expert Renovate review skill for evaluating dependency upgrade PRs, package rules, lockfile changes, grouping, automerge, and release readiness. Open dossier |
|---|---|---|---|---|
| Next steps | ||||
| Trust | ||||
| Review status | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed |
| Package trust | Package not verified | Package not verified | Package not verified | Package not verified |
| Source provenance | Submission linkedSource submission | Submission linkedSource submission | Submission linkedSource submission | Submission linkedSource submission |
| Submitter | oktofeesh1 | oktofeesh1 | oktofeesh1 | oktofeesh1 |
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — | — | — |
| Category | skills | skills | skills | skills |
| Source | Source-backed | Source-backed | Source-backed | Source-backed |
| Author | oktofeesh1 | oktofeesh1 | oktofeesh1 | oktofeesh1 |
| Added | 2026-06-03 | 2026-06-03 | 2026-06-03 | 2026-06-03 |
| Platforms | ||||
| Harness | ||||
| Source repo | — | — | — | — |
| Safety notes | ✓Installing reg-suit adds npm packages to the selected project environment; pin the reviewed package version and avoid global installs for review work. reg-suit can publish image snapshots and HTML reports through storage plugins such as S3 or Google Cloud Storage; review destination configuration before running in shared CI. Visual baselines can normalize accidental UI changes if accepted too casually; require owner approval for broad layout, color, text, or viewport changes. The source ZIP is external and version-pinned for reference; package trust should remain a maintainer decision. | ✓Installing Vitest and coverage providers adds npm packages to the selected project environment; pin reviewed versions and use project-local installs. Coverage runs execute the project test suite and can use test fixtures, network mocks, databases, or generated artifacts configured by the project. Vitest coverage can clean the configured reports directory before a run; confirm the reports directory is disposable before enabling coverage in shared workflows. Threshold changes can block or unblock CI; review threshold updates separately from test additions. The source ZIP is external and version-pinned for reference; package trust should remain a maintainer decision. | ✓Installing Spectral adds npm packages to the selected project environment; pin the reviewed version and avoid global installs for review work. Spectral can lint local files, globs, and remote contract URLs; review source locations before running checks in shared CI. Ruleset changes can silently weaken future API gates; review disabled rules, severity changes, and overrides as release-impacting changes. JavaScript rulesets and custom functions such as `.spectral.js` execute Node.js code; do not run attacker-supplied rulesets from untrusted PRs unless they have been inspected and executed in a sandboxed environment. The source ZIP is external and version-pinned for reference; package trust should remain a maintainer decision. | ✓Installing Renovate adds an npm package to the selected project environment; pin the reviewed version and avoid global installs for review work. Renovate can update dependency manifests and lockfiles; review generated diffs before approving automerge or grouped updates. Major upgrades, runtime dependencies, toolchain changes, and lockfile churn should be treated as release-blocking until tests and smoke checks pass. The source ZIP is external and version-pinned for reference; package trust should remain a maintainer decision. |
| Privacy notes | ✓Rendered UI images and reports can expose environment URLs, branch names, visible UI text, test account data, and product screenshots. Storage and notification plugins can publish report links to CI systems, pull request comments, chat tools, or cloud buckets. Keep public review notes focused on changed components, thresholds, artifact links, and summarized findings; omit sensitive rendered content that does not need to be public. | ✓Coverage output can reveal source paths, module names, uncovered function names, branch structure, report file names, and project layout. HTML, JSON, LCOV, and JUnit artifacts can include snippets, line ranges, and package structure from the reviewed project. Keep public review notes focused on aggregate gaps, file groups, risk areas, and validation commands; omit sensitive implementation details that do not need to be public. | ✓OpenAPI files can reveal internal route names, hostnames, example payloads, business object names, and planned endpoints. Lint reports can include source paths, schema paths, rule names, snippets, and examples from the reviewed contract. Keep public review notes focused on rule IDs, contract paths, compatibility impact, and summarized examples; omit details that do not need to be public. | ✓Dependency metadata can reveal package names, repository layout, branch names, internal registry hosts, and release cadence. Keep public review notes focused on package names, versions, config keys, and test results; omit operational details that do not need to be public. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | — | — | — | — |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.