Skip to content
Back to skills

Dev Visual Verdict

ASecurity

Visual regression testing — capture before/after screenshots of UI changes and compare. Use when a UI change might have unintended visual impact across components.

  • 529 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added May 29, 2026
ai-agentstestingbackend

Security analysis

A100/100

Scanned May 29, 2026

npx -y skills add evolution-foundation/evo-nexus --skill dev-visual-verdict --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Dev Visual Verdict?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Dev Visual Verdict
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/evolution-foundation-dev-visual-verdict/badge)](https://www.skillsdirectory.com/skills/evolution-foundation-dev-visual-verdict)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: dev-visual-verdict
description: Visual regression testing — capture before/after screenshots of UI changes and compare. Use when a UI change might have unintended visual impact across components.
---

# Dev Visual Verdict

Derived from oh-my-claudecode (MIT, Yeachan Heo). Adapted for the EvoNexus Engineering Layer.

Visual regression testing. Capture before/after screenshots of UI components, compare them, and flag unintended visual impact.

## Use When
- CSS / styling change that might cascade to other components
- Component refactor where the visual output should remain identical
- Theme change that needs to be verified across the app

## Do Not Use When
- Backend-only changes
- Intentional redesigns (use `@canvas-designer` instead)
- Single-component changes with obvious visual outcome

## Workflow

1. **Identify scope** — which components could be affected
2. **Capture baseline** — screenshot current state of each affected component
3. **Apply change** — let `@bolt-executor` make the modification
4. **Capture after** — screenshot post-change state
5. **Compare** — flag any visual differences (pixel-level or layout-level)
6. **Verdict** — IDENTICAL / EXPECTED CHANGES / UNEXPECTED REGRESSION

## Output
Saved to `workspace/development/verifications/[C]visual-{component}-{date}.md`:

```markdown
## Visual Verdict — {component}

### Scope
- Components checked: [list]

### Comparison
| Component | Before | After | Diff | Verdict |
|---|---|---|---|---|
| Header | ![](before-1.png) | ![](after-1.png) | 0% | IDENTICAL |
| Footer | ![](before-2.png) | ![](after-2.png) | 12% | UNEXPECTED |

### Verdict
{IDENTICAL | EXPECTED CHANGES | UNEXPECTED REGRESSION}

### Unexpected Regressions
- Footer color shifted from #1A1A1A to #2A2A2A — investigate cascade
```

## Pairs With
- `@canvas-designer` (when regression is intentional)
- `@hawk-debugger` (when regression is unintended)
- `@oath-verifier` (final visual verification)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…