update-screenshots

Name: update-screenshots
Availability: InStock
Author: Nithwin

Automates updating local screenshot baselines from CI artifacts via GitHub Actions.

Updated Mar 19, 2026

Search Tags:#automation #git #artifacts #github-actions #screenshot #ci #baselines

Ready to run

npx skills add https://github.com/Nithwin/shadowcode --skill update-screenshots-nithwin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: update-screenshots
Source: https://github.com/Nithwin/shadowcode/tree/main/.github/skills/update-screenshots
Command: npx skills add https://github.com/Nithwin/shadowcode --skill update-screenshots-nithwin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures CI-generated screenshot baselines stay in sync with the latest visuals, reducing drift between local checks and CI results.

Core Features & Use Cases

Automates retrieval of latest screenshot artifacts from GitHub Actions.
Updates local baseline assets for subsequent runs.
Provides a quick way to review diffs and resync baselines after CI changes.

Quick Start

Run the update-screenshots skill when CI reports screenshot differences or baselines need refreshing, and it will fetch the latest artifacts and commit them as new baselines.

Frequently Asked Questions about update-screenshots

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

FAQPage Schema

How do I update local screenshot baselines from GitHub Actions CI artifacts?▼

You can update local screenshot baselines by fetching the latest screenshot-diff artifacts from the Screenshot Tests workflow and committing them as new baselines under test/componentFixtures/.screenshots/baseline.

What is the best way to resync local screenshot baselines after CI reports visual diffs?▼

Automating the retrieval of latest screenshot artifacts from GitHub Actions updates local baseline assets for subsequent runs, ensuring CI-generated screenshot baselines stay in sync with the latest visuals.

Do I need gh authentication to fetch screenshot artifacts from GitHub Actions?▼

Yes, gh authentication and access to Screenshot Tests artifacts are required to fetch CI artifacts and update local screenshot baselines across branches.

When do I need to refresh screenshot baselines for my CI tests?▼

You need to refresh screenshot baselines when the Screenshot Tests workflow outputs a screenshot-diff artifact, indicating visual drift between local checks and CI results.

Why does visual drift occur between local checks and CI screenshot test results?▼

Visual drift occurs when local screenshot baselines become out of sync with the latest CI-generated visuals, requiring you to fetch latest artifacts and resync baselines after CI changes.