skills.rest
zorgentech
zorgentechOFFICIAL
Explore all skills by this author →
GitHub

visual-approve

Approve visual validation and add the visual-validation-approved label to pull requests.

Updated Aug 27, 2026
Search Tags:#automation#screenshots#github#labeling#ci#pull-request#visual-validation
One-click install
npx skills add https://github.com/zorgentech/archon --skill visual-approve
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: visual-approve
Source: https://github.com/zorgentech/archon/tree/main/.claude/skills/visual-approve
Command: npx skills add https://github.com/zorgentech/archon --skill visual-approve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evita que pull requests de frontend fiquem bloqueados por validação visual manual, simplificando a aprovação quando a validação já foi executada corretamente e sinalizando problemas críticos antes de liberar o merge.

Core Features & Use Cases

  • Verifica a existência de screenshots e do arquivo REPORT.md gerado pela validação visual para confirmar que a validação foi executada.
  • Analisa o relatório e alerta sobre problemas críticos, pedindo confirmação do usuário antes de prosseguir.
  • Automatiza a remoção da label visual-validation-pending e a adição da label visual-validation-approved, atualizando checks de status e oferecendo limpeza opcional dos arquivos de validação.
  • Use case: após revisar o relatório de um PR de frontend, adicione a aprovação visual para desbloquear pipelines que exigem esse check.

Quick Start

Approve visual validation for PR 164 and add the visual-validation-approved label if the REPORT.md and screenshots indicate no critical issues.

Frequently Asked Questions about visual-approve

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

FAQPage Schema
How do I automate visual validation approval for a pull request to unblock merging?▼

Automating visual validation approval involves verifying the existence of frontend screenshots and a REPORT.md file, then applying the visual-validation-approved label to unlock the CI merge gate.

How does visual validation labeling work in CI pipelines?▼

Visual validation labeling in CI pipelines works by automatically removing the visual-validation-pending label and adding the visual-validation-approved label to a pull request after verifying screenshots and reports.

Do I need authenticated GitHub CLI permissions to approve visual checks?▼

Yes, you need authenticated GitHub CLI permissions to perform label edits and status check updates required to approve visual checks and unlock the pull request merge.

What is the best way to handle frontend PRs blocked by manual visual validation checks?▼

The best way to handle blocked frontend PRs is to analyze the generated validation REPORT.md, alert on critical issues, and automatically update labels to signal approval for the CI pipeline.

Can I clean up visual validation screenshots and REPORT.md files after approving a PR?▼

Yes, you can optionally clean up the visual validation screenshots and REPORT.md files located under frontend/e2e/screenshots/validation/pr-<number> after updating the pull request labels.

Why does my pull request stay blocked even after visual validation screenshots are generated?▼

Your pull request stays blocked because the CI merge gate requires the visual-validation-approved label to be explicitly added after verifying the existence of the screenshots and the REPORT.md file.

Related Skills

Explore More Software Engineering Skills→
matteobortolazzomatteobortolazzo
1

verify-ui

Compare Playwright screenshots and analyze Pencil layouts for UI changes.

Community
Advanced
catu-aicatu-ai
12

harness-land

Merge an approved pull request after confirming an archived harness plan.

Official
Intermediate
dtsongdtsong
1

GitHub PR Merge

Merges GitHub pull requests via CLI or MCP with selectable strategies and automated checks.

Community
Advanced
kangju2000kangju2000
2

github

Manage GitHub pull requests, issues, workflows, releases, and repositories via the gh CLI.

Community
Intermediate