skills.rest
THRISHAL12345
THRISHAL12345COMMUNITY
Explore all skills by this author →
Website𝕏@DomaThrishalGitHub

update-screenshots

Update component screenshot baselines from CI artifacts and commit refreshed images.

Updated Aug 23, 2026
Search Tags:#screenshots#github actions#visual regression#ci#baselines
One-click install
npx skills add https://github.com/THRISHAL12345/Project_X --skill update-screenshots-thrishal12345
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-screenshots
Source: https://github.com/THRISHAL12345/Project_X/tree/main/apps/vscode-fork/.github/skills/update-screenshots
Command: npx skills add https://github.com/THRISHAL12345/Project_X --skill update-screenshots-thrishal12345

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you update and validate component screenshot baselines when CI detects visual differences, so you can keep screenshot tests aligned without manually managing repository-stored images.

Core Features & Use Cases

  • CI Screenshot Baseline Updates: Pull the latest screenshots from the CI artifact or external screenshot service when a visual regression check changes.
  • Visual Diff Investigation: Review before/after comparisons from the GitHub Action comment to understand what changed.
  • Use Case: A screenshot test fails after a UI tweak, and you need to inspect the captured images and refresh the baseline source used by the main branch merge.

Quick Start

Use the update-screenshots skill to inspect the latest CI screenshot diff and retrieve the relevant captured images for review.

Frequently Asked Questions about update-screenshots

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

FAQPage Schema
How do I update screenshot baselines after a GitHub Actions visual regression failure?▼

How screenshot baselines work is by storing component images in your repository that CI visual regression checks compare against. When a UI tweak changes a component, the check detects differences and requires downloading artifacts to review and update the stored baseline.

What is the process for resolving visual diff workflows in CI screenshot tests?▼

Resolving visual diff workflows involves inspecting before and after comparisons from GitHub Action comments, retrieving the latest captured images from CI artifacts, and committing refreshed baselines when the workflow indicates intended UI changes.

Can I use this to manage external screenshot-service baselines?▼

Yes, you can manage external screenshot-service baselines by pulling the latest screenshots from the external service when a visual regression check changes, comparing the captured images, and refreshing the baseline source used by the main branch.

Do I need to manually download CI artifacts to investigate PR review screenshot failures?▼

Yes, investigating PR review screenshot failures requires downloading CI artifacts to inspect the captured images. You compare the before and after screenshots to understand what changed before committing refreshed baselines.

When should I refresh CI screenshot baselines instead of fixing the UI code?▼

You should refresh CI screenshot baselines when the workflow indicates intended UI changes, meaning the visual differences detected by the visual regression check are deliberate updates rather than unintended visual bugs requiring code fixes.

Related Skills

Explore More Software Engineering Skills→
benzwickbenzwick

download-ci-artifacts

Download GitHub Actions CI artifacts using gh CLI commands.

Community
Intermediate
supermalangsupermalang

visual-review

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

Community
Advanced
vercel-labsvercel-labs
210

before-and-after

Capture before-and-after screenshots from two URLs or image paths.

Official
Advanced
shin0720shin0720

auto-verify

Automate visual regression testing by capturing and comparing UI screenshots with Playwright.

Community
Basic