visual-review

Read visual approval states for changed baseline images without modifying repository files.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/supermalang/ai-augmented-coding --skill visual-review-supermalang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: visual-review
Source: https://github.com/supermalang/ai-augmented-coding/tree/main/.claude/skills/visual-review
Command: npx skills add https://github.com/supermalang/ai-augmented-coding --skill visual-review-supermalang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork from visual testing by reading the approval state of changed baseline images and telling you which screenshots are ready, rejected, or still waiting on human sign-off.

Core Features & Use Cases

  • Approval-state reporting: Compares changed baseline PNGs against the integration branch and reads the visual approval record.
  • Merge gating support: Identifies approved, rejected, and pending baselines so downstream review and release steps can block safely when needed.
  • Pipeline visibility: Helps teams understand whether visual testing is enabled and whether any screenshot changes still need review.
  • Use case: A QA or PR review workflow can call this Skill to summarize every changed screenshot before allowing a merge.

Quick Start

Use the visual-review skill to report the approval status of all changed visual baselines in the current branch.

Frequently Asked Questions about visual-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check visual approval state for changed baseline images before merging a branch?

To check visual approval state for changed baseline images, compare branch changes against the integration branch and read a visual approvals record to classify screenshots as approved, rejected, or pending.

What is visual regression merge gating and how does it work with screenshot diffs?

Visual regression merge gating identifies approved, rejected, and pending baseline PNG screenshot diffs so downstream release steps can safely block a merge when human sign-off is still required.

How do I report which screenshot baselines are pending review in a git workflow?

You can report pending screenshot baselines by reading git diff and status output alongside a visual-approvals.json file to summarize which changed baseline PNGs still await human review.

Do I need specific files to classify visual testing approval states in a Claude Code pipeline?

Yes, classifying visual testing approval states requires .claude/context.md, visual-approvals.json, git diff and status output, and baseline PNGs to evaluate branch comparison and merge-gating workflows.

Does this visual review process modify repository files when reading screenshot baseline states?

No, the visual review process reads the approval state of changed baseline images without modifying repository files, ensuring the git workflow remains clean during screenshot review and merge gating.

What's the best way to summarize changed visual baselines for a QA or PR review workflow?

The best way to summarize changed visual baselines is to call a review process that reads the visual approval record and reports approved, rejected, and pending screenshots before allowing a merge.