check-visual-changes SKILL.md skillA
check-visual-changes from molefrog/moi is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add molefrog/moi/check-visual-changes@git:20261105.da3bc1dPins git:20261105.da3bc1d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- molefrog/moi
- Path
.agents/skills/check-visual-changes/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261105.da3bc1d, committed Nov 5, 2026
- Size
- 5,676 bytes
- Repository stars
- 191
- License
- a license file GitHub does not identify
Check the visual impact of an edit mid-task with `uiverify check` — render just the components you're touching on the UI Verify fleet and diff them against the real CI baseline, without opening a PR, posting a check, or moving a baseline. Works for every capture method (Storybook, Playwright, Vitest archives, and raw screenshots). Use when a coding agent has changed UI and wants a fast, authoritative "would this pass" answer before pushing — "check my visual changes…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Check your visual changes mid-edit `uiverify check` is the **interactive preview build** — the agent edit-loop counterpart to the CI `uiverify upload`. You're mid-task, you've changed a component, and you want to know *now* whether it changed anything visually and whether that change is intended — without opening a PR, waiting for CI, or touching a baseline. It renders on the **same fleet** and diffs against the **same resolved CI baseline** a real build would, so the answer is authoritative (not a local macOS screenshot that won't match Linux). But it's walled off from CI: - **No GitHub check** — invisible on the PR. - **Never advances a CI baseline.** Accepting a preview build writes a branch-scoped *preview baseline*, so your own accepted change stops re-flagging on the next check, while CI's baseline is untouched. A `changed` verdict exits 0 — it's the expected result to review, not a gate. Only a real `failed`/`blocked` or an operational error exits non-zero. ## The one rule: scope it to what you touched This is the whole point, and it's the opposite of CI. CI computes the *transitive* affected set from the …
Read the whole file at its exact version.
How to install
mdr add molefrog/moi/check-visual-changes@sha256:fc131a6decef64f3The line at the top of this page pins the label git:20261105.da3bc1d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_uqm32pu4iat3bomp)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Nov 5, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5676 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
molefrog/moi · 191 stars · license a license file GitHub does not identify · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_uqm32pu4iat3bomp GET https://markdownregistry.com/api/v1/resolve?ref=molefrog/moi/check-visual-changes GET https://markdownregistry.com/api/v1/blob/fc131a6decef64f398ba9beb584a8eeea136c1f1cdf6704a45d2c19ac5e90da8
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.